SPB Git
spboucher.ai

spb/wp30_uqo

Public

WP30: runner, chains, fan-in, transport, smoke runs (Qwen, Llama), pilot plan

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Simon-Pierre Boucher committed (Oct 30, 2026) parent fea8e12 Browse files

201 changed files +3,785 −1,269

201 changed files
Load all 201 files Unified Split
modified DECISIONS.md +3 −0
@@ -13,3 +13,6 @@ All times America/Toronto unless noted.
13 13 - **D-007 Qwen2.5 4-bit KV finding (smoke, not a result).** Both the native mlx_lm path (`generate(..., kv_bits=4)`) and the WP30 adapter produce garbage at 4-bit/group-64 for Qwen2.5-1.5B while Llama-3.2-3B survives even 2-bit/group-32 on the smoke memo. The adapter is therefore not the cause; this is the per-token affine quantization of outlier-heavy Qwen keys (the KIVI motivation). Registered as hypothesis H2; a KIVI-inspired per-channel key quantization is scheduled as a *transport-only* variant (B2b) and labelled "inspired".
14 14 - **D-008 Task families.** (i) Synthetic private-fact ledgers (generator `wp30.data.synthetic`, 15 question types per document incl. unanswerable; evaluator-only keys); (ii) public LongBench v1 subsets qasper and 2wikimqa (all 200 items each; hotpotqa reserved as a 16K-extension subset), raw jsonl from THUDM/LongBench `data.zip` because the HF loading script is no longer supported by `datasets` 5.x; (iii) executable tasks (`wp30.data.exec_tasks`, hidden tests in a `python -I` subprocess). Family (ii) is likely in pretraining corpora; family (i) is not.
15 15 - **D-009 Remote node.** M3U96b (Mac Studio M3 Ultra, 96 GB) is the second node for genuine two-node transfer: `~/wp30-worker/.venv` with the same mlx/mlx-lm pins; both 3B checkpoints downloaded there. iperf3 available on both ends for link measurement.
16 +- **D-010 Exec family difficulty (dev-only decision, 2026-10-30).** With the 7-rule specification the receiver (Qwen2.5-3B) failed even with the full ticket (A1 pass rate 0 on the smoke item: it duplicated the loop instead of composing the discount rule), so the family could not discriminate between communication methods. The specification was reduced to 6 rules with two missing in the buggy code (region exclusion, tax). Hidden tests unchanged in form (5 subsets, exact float match). Datasets regenerated before any test-split evaluation.
17 +- **D-011 Network path for E2/E6 (2026-10-30).** The laptop cannot open TCP connections to the nodes' LAN addresses (192.168.2.x; its SSH goes through Tailscale, whose ACL blocks non-SSH ports). Genuine two-node measurements therefore run **between two cluster nodes on the wired LAN**: sender/client on M3U96a (192.168.2.80), receiver worker on M3U96b (192.168.2.85). Measured link: iperf3 4 streams ≈ 940 Mbit/s (1 GbE, not 10 GbE as older notes suggested), RTT ≈ 1.2 ms. Both nodes concurrently host a CPU-light workload from another study (WP29 `claude --bare` executors); load average ≈ 1.8 on 32 cores at setup time; recorded as a limitation.
18 +- **D-012 Learned mapper scope (Track C).** Level 2 (same family, different size): Qwen2.5-1.5B → Qwen2.5-3B share the tokenizer (token-aligned), both have 2 KV heads × 128 dims but 28 vs 36 layers → per-receiver-layer linear maps from an aligned sender layer, trained on train-split caches only (reconstruction loss; optional distillation). Level 3 (cross-family Llama-3.2-3B → Qwen2.5-3B) requires tokenizer alignment by character spans; attempted only if level 2 completes; labelled "adapted (SwaT-inspired), not a SwaT reproduction" (SwaT has no public checkpoint or licence).
modified STATUS.md +5 −4
@@ -1,7 +1,8 @@
1 1 # STATUS.md — WP30
2 2
3 −**Phase:** 0 (environment + scope) — in progress
4 −**Completed gates:** none yet
5 −**Current task:** environment inspection, literature audit launch, model download
3 +**Phase:** 3→4 complete (harness + live inference + cache correctness suite 12/12), 5 in progress (text methods implemented, smoke-tested), 6 pending
4 +**Completed gates:** Phase 0 (environment, scope), Phase 1 (literature audit: 34 sources, 3 audit files), Phase 2 (datasets: 800 items, keys isolated, 0 cross-split duplicates), Phase 3 (E0 smoke: 114 trials, real generation), Phase 4 (tests/test_cache_correctness.py 12 passed)
5 +**Current task:** pilot config, Llama receiver smoke, chain/fan-in smoke, remote worker (M3U96b) for E2/E6
6 6 **Blockers:** none
7 −**Next command:** `python -m wp30 doctor --output evidence/environment.json` (after package scaffold)
7 +**Resume:** `source .venv/bin/activate && python -m wp30 run --config configs/pilot.yaml --resume`
8 +**Run IDs so far:** E0_smoke (runs/raw/E0_smoke.jsonl)
added configs/chains_smoke.yaml +11 −0
@@ -0,0 +1,11 @@
1 +experiment_id: E4_smoke
2 +splits: [dev]
3 +lengths: [2000]
4 +limit_docs: 1
5 +hops: [1, 2]
6 +budget_tokens: 512
7 +max_fetch_bytes: 1500
8 +max_lookups: 4
9 +chains:
10 + - {representation: A4, mode: closed, agents: [qwen3b]}
11 + - {representation: A5, mode: repairable, agents: [qwen3b, llama3b]}
added configs/fanin_smoke.yaml +9 −0
@@ -0,0 +1,9 @@
1 +experiment_id: E5_smoke
2 +splits: [dev]
3 +lengths: [2000]
4 +limit_docs: 2
5 +fan_in: [2]
6 +budget_tokens: 512
7 +sender: qwen3b
8 +aggregator: qwen3b
9 +methods: [full_context, concat_A4, merge_A5, shared_memory_A6, cache_concat_negative_control]
added configs/pilot.yaml +43 −0
@@ -0,0 +1,43 @@
1 +experiment_id: E1_pilot
2 +splits: [dev]
3 +families: [synthetic, exec, public_qasper, public_2wikimqa]
4 +lengths: [2000, 8000]
5 +limit_docs_per_family: 6
6 +max_questions_per_doc: 8
7 +model_pairs:
8 + - {sender: qwen3b, receiver: qwen3b}
9 + - {sender: llama3b, receiver: llama3b}
10 +generation: {max_tokens: 48, per_family: {exec: 320}}
11 +seeds: [0]
12 +conditions:
13 + - {method: A0}
14 + - {method: A1}
15 + - {method: A2, budget_tokens: 128}
16 + - {method: A2, budget_tokens: 512}
17 + - {method: A3, budget_tokens: 128, access: blind}
18 + - {method: A3, budget_tokens: 512, access: blind}
19 + - {method: A3, budget_tokens: 512, access: aware}
20 + - {method: A4, budget_tokens: 128, access: blind}
21 + - {method: A4, budget_tokens: 512, access: blind}
22 + - {method: A4, budget_tokens: 512, access: aware}
23 + - {method: A5, budget_tokens: 128, access: blind}
24 + - {method: A5, budget_tokens: 512, access: blind}
25 + - {method: A5, budget_tokens: 512, access: aware}
26 + - {method: A6, budget_tokens: 512, access: blind, max_fetch_bytes: 2000, max_lookups: 6}
27 + - {method: A7, codec: zstd}
28 + - {method: A8, budget_tokens: 512, access: blind}
29 + - {method: B0}
30 + - {method: B1}
31 + - {method: B2, bits: 8}
32 + - {method: B2, bits: 4}
33 + - {method: B2, bits: 2, group_size: 32}
34 + - {method: B3, keep_frac: 0.5}
35 + - {method: B3, keep_frac: 0.25}
36 + - {method: B3, keep_frac: 0.125}
37 + - {method: B4, keep_frac: 0.25}
38 + - {method: B5, keep_frac: 0.5, access: aware}
39 + - {method: B5, keep_frac: 0.25, access: aware}
40 + - {method: B5, keep_frac: 0.125, access: aware}
41 + - {method: B5, keep_frac: 0.25, access: blind}
42 + - {method: B6, keep_frac: 0.25, access: aware}
43 + - {method: B9, keep_frac: 0.25, bits: 8, access: aware, policy: attention}
modified configs/smoke.yaml +1 −1
@@ -6,7 +6,7 @@ limit_docs_per_family: 1
6 6 max_questions_per_doc: 4
7 7 model_pairs:
8 8 - {sender: qwen3b, receiver: qwen3b}
9 −generation: {max_tokens: 48}
9 +generation: {max_tokens: 48, per_family: {exec: 320}}
10 10 seeds: [0]
11 11 conditions:
12 12 - {method: A0}
modified data/generated/docs/exec/exec_00001_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00001_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-7019: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 20 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 47.53, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 18, \"unit_price\": 4.14, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 25, \"unit_price\": 71.73, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 9.99, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 50.46, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 13, \"unit_price\": 26.95, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 8073,
7 − "document_hash": "ddfe7fcc3baca3e97144b66188f285a0e8a83018d1ca41b7f37cb80dede62dcc",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-7019: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 20 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 47.53, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 18, \"unit_price\": 4.14, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 25, \"unit_price\": 71.73, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 9.99, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 50.46, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 13, \"unit_price\": 26.95, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7894,
7 + "document_hash": "72a702cc7076fb313f97772498675d83532bf6ce59f1d3cbf3bb86fa387dc0e6",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00002_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00002_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6302: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 3 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 39, \"unit_price\": 5.2, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 40, \"unit_price\": 14.07, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 28, \"unit_price\": 51.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 18, \"unit_price\": 37.06, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 37, \"unit_price\": 67.53, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 13.36, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 8001,
7 − "document_hash": "7918e3cdcab2a8bfae77558b7b523f4cea70cdc52435393d98d0c7b36de29e60",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6302: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 3 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 39, \"unit_price\": 5.2, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 40, \"unit_price\": 14.07, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 28, \"unit_price\": 51.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 18, \"unit_price\": 37.06, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 37, \"unit_price\": 67.53, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 13.36, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7819,
7 + "document_hash": "7ec85eb17fda1c57c2a77a31dc79bf35b3c62974f6f1905e409880cbe869b6f5",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00003_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00003_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6542: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"delta\", \"units\": 11, \"unit_price\": 35.12, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 26, \"unit_price\": 47.96, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 19, \"unit_price\": 11.96, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 34, \"unit_price\": 27.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 8.05, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 26, \"unit_price\": 37.32, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 13}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 7972,
7 − "document_hash": "8ab845867bddfdcb5cf63b1319a6f29794cc9dddea45cd92bca3bc94fe023da7",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6542: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"delta\", \"units\": 11, \"unit_price\": 35.12, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 26, \"unit_price\": 47.96, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 19, \"unit_price\": 11.96, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 34, \"unit_price\": 27.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 8.05, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 26, \"unit_price\": 37.32, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 13}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7793,
7 + "document_hash": "f7d729b32469d142625681408a1dd1aa3d1d99a7c07adb645c9f40d7550e8695",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00004_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00004_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4473: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 22 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 6, \"unit_price\": 66.62, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 75.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 70.75, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 27, \"unit_price\": 56.79, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 16, \"unit_price\": 23.1, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 64.58, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 8037,
7 − "document_hash": "08c5cdfaa7a0742a094ee4726d97a32a89395c354270406bbcf78eff4fdbe8b2",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4473: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 22 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 6, \"unit_price\": 66.62, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 75.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 70.75, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 27, \"unit_price\": 56.79, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 16, \"unit_price\": 23.1, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 64.58, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7855,
7 + "document_hash": "aeca575de77be2cf25f1c9f8e053485ad918ef4b3468680a4ef6bfa3b8cb781b",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00005_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00005_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-1004: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 9.69, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 33, \"unit_price\": 9.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 36, \"unit_price\": 26.91, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 12.59, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 4, \"unit_price\": 49.06, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 15, \"unit_price\": 38.72, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 8031,
7 − "document_hash": "f885d791d02ed1adb010c9c27804b5c38facf8fd2a09b9b1b6f9cacb7b0acc81",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-1004: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 9.69, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 33, \"unit_price\": 9.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 36, \"unit_price\": 26.91, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 12.59, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 4, \"unit_price\": 49.06, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 15, \"unit_price\": 38.72, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7852,
7 + "document_hash": "c5e26772985f1897f27e3729a56bdf95e08ba4718b928a1480572409c422c83f",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00006_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00006_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-2483: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 23 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"beta\", \"units\": 40, \"unit_price\": 51.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 27, \"unit_price\": 16.15, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 2, \"unit_price\": 75.62, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 6, \"unit_price\": 55.85, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 38, \"unit_price\": 45.09, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 23, \"unit_price\": 32.92, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 8049,
7 − "document_hash": "2a1bb6d86c77861b166e281bb1deac9a658ed4383a7ade93e9698e33861de0e5",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-2483: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 23 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"beta\", \"units\": 40, \"unit_price\": 51.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 27, \"unit_price\": 16.15, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 2, \"unit_price\": 75.62, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 6, \"unit_price\": 55.85, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 38, \"unit_price\": 45.09, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 23, \"unit_price\": 32.92, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7867,
7 + "document_hash": "283461ef1dfaf2225620026d081a07116ec5fa2173ffa118704c0cf1d53a2eac",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00007_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00007_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6853: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 3 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 15.79, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 21.54, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 27.04, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 8, \"unit_price\": 48.03, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 12, \"unit_price\": 59.99, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 24, \"unit_price\": 79.62, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 9}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 7826,
7 − "document_hash": "fb0150ce17a4b0ade1601cf6082b82e83f67db83a57c177064777d028b33d97c",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6853: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 3 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 15.79, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 21.54, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 27.04, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 8, \"unit_price\": 48.03, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 12, \"unit_price\": 59.99, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 24, \"unit_price\": 79.62, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 9}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7644,
7 + "document_hash": "961b89accd7b0332a165c291bb3c527fd00bea183807cff965326b5f758f1b7f",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00008_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00008_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-9591: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 15 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 20, \"unit_price\": 27.18, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 55.08, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 11, \"unit_price\": 28.44, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 3, \"unit_price\": 59.67, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 79.85, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 26.43, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 8052,
7 − "document_hash": "04f896fa681f3ae7cbfc7efa30fd96c43be9d9b703dab76457ee8043483b3612",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-9591: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 15 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 20, \"unit_price\": 27.18, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 55.08, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 11, \"unit_price\": 28.44, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 3, \"unit_price\": 59.67, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 79.85, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 26.43, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7873,
7 + "document_hash": "4ad9a1fbe7db8f523841d367742505a5c92581010a15fdabb2bb6b6d77afbaa4",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00009_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00009_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4251: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 10.7, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 19, \"unit_price\": 48.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 5.34, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 29, \"unit_price\": 46.92, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 44.75, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 15, \"unit_price\": 42.63, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 8097,
7 − "document_hash": "db44cbab6b33239dddaa205976960167be792c1b1025bd39a4c4d6cf0f6ab7d7",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4251: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 10.7, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 19, \"unit_price\": 48.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 5.34, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 29, \"unit_price\": 46.92, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 44.75, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 15, \"unit_price\": 42.63, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7916,
7 + "document_hash": "7c7609e3e3780713446d7ec4cbe48dba3ad69a1bf6d96393eb7e34fe13581d81",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00010_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00010_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-7892: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 8 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 25.77, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 67.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 9, \"unit_price\": 78.75, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 19, \"unit_price\": 47.19, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 61.6, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 64.37, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 8004,
7 − "document_hash": "232fe52471a905a3ae14b591781c17dfa57a2d115258bfc1f8a1fce231b705ad",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-7892: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 8 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 25.77, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 67.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 9, \"unit_price\": 78.75, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 19, \"unit_price\": 47.19, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 61.6, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 64.37, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7825,
7 + "document_hash": "2951e556f1045edd4bb9926de1dac81793260ddcd823e8c6abe38566b4cbcc07",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00011_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00011_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-1386: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 23 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 19, \"unit_price\": 66.05, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 28.06, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 44.45, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 7, \"unit_price\": 66.72, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 24, \"unit_price\": 6.84, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 20, \"unit_price\": 64.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 8135,
7 − "document_hash": "f046c8292307adf97cae067d41f5a7bcce9d2a48bc8dd143e0f11e89a1c3a4c2",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-1386: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 23 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 19, \"unit_price\": 66.05, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 28.06, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 44.45, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 7, \"unit_price\": 66.72, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 24, \"unit_price\": 6.84, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 20, \"unit_price\": 64.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7953,
7 + "document_hash": "6b5b870bbcdf744c667890cf6185717b10f87e45ad7a6ccada501987d53f5e6d",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00012_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00012_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-3390: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 10 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 6, \"unit_price\": 45.84, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 22, \"unit_price\": 28.76, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 29, \"unit_price\": 22.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 25, \"unit_price\": 38.56, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 52.18, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 46.81, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 7906,
7 − "document_hash": "2befcba5bfd5b509a9a6ec5d9334e2e384a05b6733ac02d80222302d3ca6e6ef",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-3390: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 10 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 6, \"unit_price\": 45.84, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 22, \"unit_price\": 28.76, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 29, \"unit_price\": 22.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 25, \"unit_price\": 38.56, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 52.18, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 46.81, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7724,
7 + "document_hash": "8991dd153dfd83b4a1aea0eb4340aabe4370ac72ef16427f5f67894ac175edde",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00013_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00013_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8332: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 20 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 25, \"unit_price\": 19.02, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 30, \"unit_price\": 31.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 37, \"unit_price\": 6.76, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 3, \"unit_price\": 50.8, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 12, \"unit_price\": 70.92, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 29.26, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 8051,
7 − "document_hash": "d006207e385cff8703be29071faf5845de84d05d8a677e40dda4983739115d29",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8332: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 20 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 25, \"unit_price\": 19.02, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 30, \"unit_price\": 31.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 37, \"unit_price\": 6.76, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 3, \"unit_price\": 50.8, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 12, \"unit_price\": 70.92, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 29.26, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7870,
7 + "document_hash": "ee93ee22294a4463cb6cf9ca3d5ab7ea7fd2a991b2b55448f089c2290e51a174",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00014_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00014_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-7580: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 17, \"unit_price\": 20.49, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 9, \"unit_price\": 61.62, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 16, \"unit_price\": 28.29, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 10, \"unit_price\": 53.03, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 40, \"unit_price\": 5.5, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 30, \"unit_price\": 60.89, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 8089,
7 − "document_hash": "e6ac9234df3fc7dcec86770e041bf75b576d1c65cf6fe32717891429f5461066",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-7580: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 17, \"unit_price\": 20.49, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 9, \"unit_price\": 61.62, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 16, \"unit_price\": 28.29, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 10, \"unit_price\": 53.03, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 40, \"unit_price\": 5.5, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 30, \"unit_price\": 60.89, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7910,
7 + "document_hash": "b25f9d4fb9c997b0cb6e19983b48490097f6592b8d17e66f305f5a1b3e8a8443",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00015_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00015_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-7400: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 10 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 44.28, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 77.11, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 13.36, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 22, \"unit_price\": 37.27, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 24.21, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 4, \"unit_price\": 49.63, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 8041,
7 − "document_hash": "7bd733e903db470812271aa82f1cd9c7111ace0dcd257ace35b07e660d045be7",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-7400: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 10 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 44.28, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 77.11, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 13.36, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 22, \"unit_price\": 37.27, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 24.21, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 4, \"unit_price\": 49.63, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7859,
7 + "document_hash": "7334bc5b260e11b2b0cdf9db05839cac2f397ae0e44db4e8bba7559dc94036bb",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00016_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00016_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8263: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 4, \"unit_price\": 16.09, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 38, \"unit_price\": 13.92, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 27, \"unit_price\": 31.16, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 21, \"unit_price\": 76.19, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 37, \"unit_price\": 43.73, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 41.2, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 8045,
7 − "document_hash": "b232fee620440e55facf033b892741387c97661b269dc2371313fb0f5934ff69",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8263: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 4, \"unit_price\": 16.09, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 38, \"unit_price\": 13.92, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 27, \"unit_price\": 31.16, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 21, \"unit_price\": 76.19, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 37, \"unit_price\": 43.73, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 41.2, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7864,
7 + "document_hash": "6a5268852caa8dc3015fd42e678e912f463ba061ac417b09de9ac6ed45e85d7f",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00017_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00017_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-5234: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 71.87, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 31, \"unit_price\": 57.69, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 11, \"unit_price\": 63.43, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 39, \"unit_price\": 73.64, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 41.11, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 17, \"unit_price\": 36.3, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 8053,
7 − "document_hash": "bce532bd3702b32e6eb3620ef3ea7d860a695f22bb90b8e995836a7937c77f52",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-5234: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 71.87, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 31, \"unit_price\": 57.69, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 11, \"unit_price\": 63.43, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 39, \"unit_price\": 73.64, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 41.11, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 17, \"unit_price\": 36.3, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7872,
7 + "document_hash": "f2d06422bd98b400b7401ce4c5ae2939aeb43f51482e84cba0c0e3c0845c71a5",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00018_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00018_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-3864: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 24, \"unit_price\": 62.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 12, \"unit_price\": 68.54, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 5, \"unit_price\": 63.9, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 19, \"unit_price\": 71.94, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 27, \"unit_price\": 9.36, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 25, \"unit_price\": 26.85, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 2}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 8169,
7 − "document_hash": "6f0951d7af338593059efbe431f0b7ce5bf9ae652e3dfb9eedafa7e192b80c01",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-3864: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 24, \"unit_price\": 62.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 12, \"unit_price\": 68.54, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 5, \"unit_price\": 63.9, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 19, \"unit_price\": 71.94, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 27, \"unit_price\": 9.36, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 25, \"unit_price\": 26.85, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 2}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7990,
7 + "document_hash": "f219110fda4e5d20fabbe592248da3e78f61f411dbc16b9412d9b8d692eda870",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00019_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00019_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4945: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 55.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 5.96, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 35.2, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 18, \"unit_price\": 18.49, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 18, \"unit_price\": 38.49, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 40, \"unit_price\": 46.09, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 8031,
7 − "document_hash": "733853d52a559dfc67d0cdab02de9e21c2aa09e0b25702d2cadfb38c20ab2159",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4945: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 55.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 5.96, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 35.2, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 18, \"unit_price\": 18.49, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 18, \"unit_price\": 38.49, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 40, \"unit_price\": 46.09, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7849,
7 + "document_hash": "232819b55ebc60215845a14aaf01c04a94dc7902933c03a47546ec41ee16502f",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00020_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00020_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8600: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 77.87, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 14, \"unit_price\": 51.72, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 19, \"unit_price\": 11.75, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 67.82, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 22.1, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 15, \"unit_price\": 49.46, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 − "char_len": 8080,
7 − "document_hash": "1a7bfffc3347254640c8b76b9b5f0ff368a758543995fa06006e28ea43d8eb71",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8600: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 77.87, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 14, \"unit_price\": 51.72, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 19, \"unit_price\": 11.75, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 67.82, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 22.1, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 15, \"unit_price\": 49.46, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 + "char_len": 7901,
7 + "document_hash": "862136f6ccb7f77097086ceddd84945e55b7df17401a63b0ce306740969966e5",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00101_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00101_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-1234: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 53.66, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 34, \"unit_price\": 17.65, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 66.62, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 35, \"unit_price\": 33.18, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 47.37, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 4, \"unit_price\": 22.46, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 8125,
7 − "document_hash": "932bac511f2c5ee3faf8c1f37b853fcd2be373db29c6a84b2d7f8c3ab71ee6f9",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-1234: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 53.66, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 34, \"unit_price\": 17.65, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 66.62, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 35, \"unit_price\": 33.18, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 47.37, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 4, \"unit_price\": 22.46, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7944,
7 + "document_hash": "c8bf1a72f33c0fc6f87af8c3029f12cbff489bcb95ae36398cd522af1811a74f",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00102_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00102_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4681: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 31, \"unit_price\": 68.35, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 65.24, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 17, \"unit_price\": 8.56, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 36, \"unit_price\": 48.5, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 22, \"unit_price\": 76.92, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 24, \"unit_price\": 51.48, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 8089,
7 − "document_hash": "5535ac3109616f7d46dff5417535ca232754aee2c0759e072d552e465f004d46",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4681: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 31, \"unit_price\": 68.35, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 65.24, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 17, \"unit_price\": 8.56, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 36, \"unit_price\": 48.5, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 22, \"unit_price\": 76.92, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 24, \"unit_price\": 51.48, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7910,
7 + "document_hash": "61b6c7bb86261a26bf000996edd5f9326f7f77ca1c37085fd999cddf1bff2396",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00103_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00103_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-1178: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 26 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 6, \"unit_price\": 24.8, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 13.68, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 26.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 10.58, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 34.11, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 17.34, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 8038,
7 − "document_hash": "a7875d1e95742c6246c4ec3862b9797a4269a2b607e47869f5014d7dc29139e0",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-1178: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 26 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 6, \"unit_price\": 24.8, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 13.68, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 26.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 10.58, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 34.11, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 17.34, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7856,
7 + "document_hash": "596ef1cd6d37fdac729520a738ed129e4ffaf619d372ad869d8188a0a5cac1ef",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00104_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00104_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6532: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 22, \"unit_price\": 26.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 59.29, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 50.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 74.61, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 40.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 29.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 8014,
7 − "document_hash": "bce3091895fc315bf981ac1272a7da1f00b0f64819f1ecfa2a6dd8a3d23f2207",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6532: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 22, \"unit_price\": 26.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 59.29, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 50.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 74.61, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 40.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 29.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7835,
7 + "document_hash": "6b4aadaf1b71672d6d8aed5a412c7aa490e3e0eb1c92e5df6db1cc9554f83483",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00105_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00105_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-2817: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 33, \"unit_price\": 44.66, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 21, \"unit_price\": 12.84, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 71.25, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 69.08, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 39, \"unit_price\": 71.78, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 38, \"unit_price\": 17.58, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 8046,
7 − "document_hash": "fe4b8857bf1774be1123bec85a5743da5c3551d53125ddf128efde401f3990c2",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-2817: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 33, \"unit_price\": 44.66, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 21, \"unit_price\": 12.84, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 71.25, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 69.08, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 39, \"unit_price\": 71.78, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 38, \"unit_price\": 17.58, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7867,
7 + "document_hash": "a59face90fe592d3d8a9b375aafefb775631dd798a60a424f981cceae1ec2996",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00106_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00106_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8363: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 66.67, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 26, \"unit_price\": 69.05, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 9, \"unit_price\": 67.57, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 49.2, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 34, \"unit_price\": 40.78, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 31, \"unit_price\": 40.56, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 7943,
7 − "document_hash": "c3652bfa1632f0cc62d6512131ef519100143881225c8b4ee572c1876e7c6c7f",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8363: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 66.67, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 26, \"unit_price\": 69.05, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 9, \"unit_price\": 67.57, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 49.2, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 34, \"unit_price\": 40.78, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 31, \"unit_price\": 40.56, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7761,
7 + "document_hash": "a78f55af374fd04eb589b193a9eca2f84cf04bcdb3fa60aaeb29fbe358c79464",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00107_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00107_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-7434: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 23, \"unit_price\": 30.74, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 29, \"unit_price\": 4.67, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 2, \"unit_price\": 67.07, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 10.41, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 20, \"unit_price\": 61.47, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 17, \"unit_price\": 16.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 7930,
7 − "document_hash": "983dbcacdfae2acf0316690a7fe50cfa2523ae41beffd9de42356f2ebd3d1e79",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-7434: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 23, \"unit_price\": 30.74, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 29, \"unit_price\": 4.67, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 2, \"unit_price\": 67.07, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 10.41, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 20, \"unit_price\": 61.47, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 17, \"unit_price\": 16.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7751,
7 + "document_hash": "83ea6e4f6c5d3a6eed7a921a930819d760ffb3dac7c22761dc9b4c28084904cc",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00108_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00108_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-5898: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 13 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 16, \"unit_price\": 59.1, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 47.72, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 24.32, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 18, \"unit_price\": 53.1, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 33.13, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 28, \"unit_price\": 58.35, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 − "char_len": 8038,
7 − "document_hash": "7ebb05d3714e237d074dfc9a69c5b83e99932f9041b5d4fe15c8fc7224ba7078",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-5898: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 13 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 16, \"unit_price\": 59.1, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 47.72, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 24.32, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 18, \"unit_price\": 53.1, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 33.13, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 28, \"unit_price\": 58.35, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 + "char_len": 7859,
7 + "document_hash": "b9ccaaf72598ea6e12a10942f2697dd01ca891115b652043a2f6ce4cb68570cc",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00109_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00109_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-1880: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 14 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 16.34, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 14, \"unit_price\": 77.14, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 21.7, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 3, \"unit_price\": 65.34, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 25, \"unit_price\": 36.24, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 22, \"unit_price\": 37.17, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 8073,
7 − "document_hash": "680dab47e67683cb351941eea647197cb2b2ea472ff116582019ace0c543d461",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-1880: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 14 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 16.34, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 14, \"unit_price\": 77.14, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 21.7, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 3, \"unit_price\": 65.34, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 25, \"unit_price\": 36.24, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 22, \"unit_price\": 37.17, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7894,
7 + "document_hash": "d53ada6a135b4827dcacb2ebec142b5000ad21961fb0cd199fc7c609424d4d5a",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00110_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00110_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-2821: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 48.78, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 22, \"unit_price\": 37.65, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 10, \"unit_price\": 52.8, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 25, \"unit_price\": 30.46, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 17, \"unit_price\": 18.59, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 18, \"unit_price\": 26.04, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 1)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 − "char_len": 8019,
7 − "document_hash": "f1699da28903736ad58ec0640a277bb2eac030c80c49c22c027c273374df86fa",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-2821: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 48.78, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 22, \"unit_price\": 37.65, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 10, \"unit_price\": 52.8, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 25, \"unit_price\": 30.46, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 17, \"unit_price\": 18.59, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 18, \"unit_price\": 26.04, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 + "char_len": 7840,
7 + "document_hash": "789f1f1a750d514137a988d21a0807cc30c8548da830f2eeef66854fc179fcf5",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00111_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00111_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8832: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 74.2, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 2, \"unit_price\": 62.29, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 46.48, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 49.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 38, \"unit_price\": 62.57, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 38.23, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 7942,
7 − "document_hash": "e65e9534b60b15cdaadf465396c6385868f5a0ed4be5ba04c458937c2eff43ae",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8832: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 74.2, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 2, \"unit_price\": 62.29, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 46.48, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 49.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 38, \"unit_price\": 62.57, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 38.23, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7763,
7 + "document_hash": "9f3d9d2caa1830b0bf0b983179f4de3251ec9bb8648c710bf43f0fb6c531ef85",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00112_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00112_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-1935: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"gamma\", \"units\": 4, \"unit_price\": 38.52, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 13, \"unit_price\": 23.87, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 15, \"unit_price\": 18.69, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 55.47, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 36, \"unit_price\": 19.76, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 61.42, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 − "char_len": 7996,
7 − "document_hash": "4a8db801f5e7f6b2108618514f90c37fbdbb61e902c4441c0d68548a5792da05",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-1935: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"gamma\", \"units\": 4, \"unit_price\": 38.52, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 13, \"unit_price\": 23.87, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 15, \"unit_price\": 18.69, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 55.47, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 36, \"unit_price\": 19.76, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 61.42, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 + "char_len": 7814,
7 + "document_hash": "182cf1cbb5939b7e1ca9170096aa77a9cc3c2c4f8efb3195e8b4ad19b77a3f46",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00113_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00113_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-7037: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 13 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 20, \"unit_price\": 39.93, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 30, \"unit_price\": 5.13, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 32, \"unit_price\": 20.94, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 14, \"unit_price\": 3.69, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 5, \"unit_price\": 42.33, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 3, \"unit_price\": 57.2, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 8055,
7 − "document_hash": "7535b4d324a3e28b457e40fe41d18d52e75a9ed0271b411285e522c6c8c8200e",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-7037: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 13 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 20, \"unit_price\": 39.93, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 30, \"unit_price\": 5.13, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 32, \"unit_price\": 20.94, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 14, \"unit_price\": 3.69, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 5, \"unit_price\": 42.33, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 3, \"unit_price\": 57.2, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7874,
7 + "document_hash": "c89720bd112bca637c8fa3b4a98f7cc41a384be468eee47f5c44607ee6fc46f1",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00114_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00114_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-7391: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 15 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 39.73, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 65.95, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 38, \"unit_price\": 38.36, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 2, \"unit_price\": 45.5, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 23, \"unit_price\": 30.46, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 8, \"unit_price\": 10.31, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 6}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 8042,
7 − "document_hash": "e1faab8175075b8cf98d2e5e16181db3f5a8f103ed89d35efee7ba4684968699",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-7391: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 15 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 39.73, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 65.95, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 38, \"unit_price\": 38.36, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 2, \"unit_price\": 45.5, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 23, \"unit_price\": 30.46, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 8, \"unit_price\": 10.31, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 6}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7863,
7 + "document_hash": "86a377fe8f0559479ca21128972c50d14bd9e19d38d2bf49f763d402259c0aad",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00115_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00115_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4157: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 8 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 62.27, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 35, \"unit_price\": 64.7, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 2, \"unit_price\": 29.09, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 8, \"unit_price\": 18.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 17.85, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 32, \"unit_price\": 53.93, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 12}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.",
6 − "char_len": 8127,
7 − "document_hash": "4d6a9aa137c992493ef42f6758dbb35b873a4a392b00eae7152d6e45b68a3c1b",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4157: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 8 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 62.27, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 35, \"unit_price\": 64.7, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 2, \"unit_price\": 29.09, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 8, \"unit_price\": 18.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 17.85, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 32, \"unit_price\": 53.93, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 12}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.",
6 + "char_len": 7946,
7 + "document_hash": "33ee1d20ea5713048e1335d3786ba0b10b3a5998a16200f09823d0c4cf0dcbe1",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00116_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00116_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8712: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 40.17, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 3, \"unit_price\": 67.68, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 1, \"unit_price\": 21.59, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 40, \"unit_price\": 21.98, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 6, \"unit_price\": 30.51, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 11, \"unit_price\": 66.45, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 7941,
7 − "document_hash": "2b6100ff4b04865ebf622b9749757f3b32215faa2e32f12d63be71b0c18fc7be",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8712: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 27, \"unit_price\": 40.17, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 3, \"unit_price\": 67.68, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 1, \"unit_price\": 21.59, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 40, \"unit_price\": 21.98, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 6, \"unit_price\": 30.51, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 11, \"unit_price\": 66.45, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7762,
7 + "document_hash": "379dcf9e9ada65463c8d73e2cbb54ff33c8c46ea3154539a1d6df25bab2a0a0e",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00117_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00117_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8902: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 34.17, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 11, \"unit_price\": 39.09, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 37.26, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 35, \"unit_price\": 13.43, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 19, \"unit_price\": 4.12, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 1, \"unit_price\": 4.15, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 8064,
7 − "document_hash": "6e53d886a35d8e51c98908f1e40e9314353c62a19e3197603509fd2a59c6bbf3",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8902: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 34.17, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 11, \"unit_price\": 39.09, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 37.26, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 35, \"unit_price\": 13.43, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 19, \"unit_price\": 4.12, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 1, \"unit_price\": 4.15, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7883,
7 + "document_hash": "34a1cc9614d0c2d2f9766b2968ae3fa3eb2b6cc1a372750650ae7f7359325896",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00118_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00118_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8999: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 68.73, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 35.36, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 15, \"unit_price\": 65.25, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 8, \"unit_price\": 18.19, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 2, \"unit_price\": 53.23, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 48.57, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 − "char_len": 8050,
7 − "document_hash": "5353584056feb451c43bd2199aa87e2f7064bbfb9485b6eb1f6a1387dddac0f6",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8999: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 68.73, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 35.36, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 15, \"unit_price\": 65.25, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 8, \"unit_price\": 18.19, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 2, \"unit_price\": 53.23, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 48.57, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 + "char_len": 7868,
7 + "document_hash": "58d2108f993d9baafb67222dc4bd97895639cb6c2410e675e3ed2c4233c8fee4",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00119_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00119_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6430: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 17 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 25, \"unit_price\": 38.28, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 32, \"unit_price\": 28.27, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 56.96, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 58.1, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 21, \"unit_price\": 7.09, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 20, \"unit_price\": 10.91, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 7901,
7 − "document_hash": "f62c9b5ecd91caa0cf95af49bf6d40dd2bc3885255008434f482e56b7a2a2fae",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6430: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 17 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 25, \"unit_price\": 38.28, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 32, \"unit_price\": 28.27, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 56.96, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 58.1, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 21, \"unit_price\": 7.09, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 20, \"unit_price\": 10.91, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7722,
7 + "document_hash": "98f121e7a33ff30acfcaf7a0346bbc04cc9f508e092e316490793765a8e0ab09",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00120_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00120_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6138: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 26, \"unit_price\": 76.39, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 2, \"unit_price\": 45.78, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 27, \"unit_price\": 55.23, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 33, \"unit_price\": 48.6, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 31.92, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 33.32, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 5}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 7992,
7 − "document_hash": "5b1b1089a793b0953579b8ce004efe99282ffd8a6eb17b16c3ce50273c121aad",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6138: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 26, \"unit_price\": 76.39, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 2, \"unit_price\": 45.78, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 27, \"unit_price\": 55.23, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 33, \"unit_price\": 48.6, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 31.92, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 33.32, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 5}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7811,
7 + "document_hash": "c5be33e5009123ba2c251884304b839ae6fc5163f0745c302cffbabf618b40cb",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00121_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00121_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6726: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"beta\", \"units\": 4, \"unit_price\": 48.97, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 58.75, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 27, \"unit_price\": 78.34, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 30, \"unit_price\": 65.31, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 52.31, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 37, \"unit_price\": 9.99, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 − "char_len": 8033,
7 − "document_hash": "9064e893e331010c27db6e1229c2af7da83ed7fb3680e079fc5c1a9ee7b2d73a",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6726: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"beta\", \"units\": 4, \"unit_price\": 48.97, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 58.75, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 27, \"unit_price\": 78.34, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 30, \"unit_price\": 65.31, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 52.31, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 37, \"unit_price\": 9.99, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 + "char_len": 7854,
7 + "document_hash": "1645df3901b5bd61ea8c6790e15a695b1144eef69bc075121ffd0c83e6fc13af",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00122_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00122_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8821: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"delta\", \"units\": 12, \"unit_price\": 43.53, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 74.34, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 29, \"unit_price\": 31.64, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 12.23, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 24.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 38, \"unit_price\": 69.36, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 12}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 8139,
7 − "document_hash": "8641f3a09b033f2a216948ea197682c280cda7a9559b7102473da5f152a73eb3",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8821: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"delta\", \"units\": 12, \"unit_price\": 43.53, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 74.34, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 29, \"unit_price\": 31.64, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 12.23, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 24.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 38, \"unit_price\": 69.36, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 12}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7960,
7 + "document_hash": "bd26e436a86876d04961cc142588671db4ead753f838933bde6907da5354f70e",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00123_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00123_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6186: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 17 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 44.11, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 43.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 30, \"unit_price\": 27.36, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 15, \"unit_price\": 68.15, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 1, \"unit_price\": 49.94, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 34, \"unit_price\": 57.03, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 8069,
7 − "document_hash": "3a8a85801b1200bb0a18063e20eb67097e3e9c34d009894a5a61963f7145608b",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6186: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 17 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 44.11, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 43.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 30, \"unit_price\": 27.36, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 15, \"unit_price\": 68.15, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 1, \"unit_price\": 49.94, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 34, \"unit_price\": 57.03, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7890,
7 + "document_hash": "6c868c5916de1b984d70dc327ee458814726f8ea6a1fad99f8c2fb35e7e77b7f",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00124_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00124_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4820: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 24, \"unit_price\": 15.43, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 11, \"unit_price\": 16.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 4, \"unit_price\": 32.63, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 25, \"unit_price\": 22.72, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 35, \"unit_price\": 53.2, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 13, \"unit_price\": 66.87, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 7919,
7 − "document_hash": "adfa94aa242540ae900f58c2db73dace6e0bb6ec243a71137685b2d527e54fdb",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4820: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 24, \"unit_price\": 15.43, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 11, \"unit_price\": 16.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 4, \"unit_price\": 32.63, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 25, \"unit_price\": 22.72, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 35, \"unit_price\": 53.2, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 13, \"unit_price\": 66.87, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7740,
7 + "document_hash": "a285cd3f7f5bbfcaa508697bf261341dc847483a97e354b95faf09bc23bb626f",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00125_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00125_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8156: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 74.86, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 79.31, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 24.62, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 17, \"unit_price\": 61.06, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 4, \"unit_price\": 48.73, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 73.41, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 7915,
7 − "document_hash": "144a4af055228fc4045ad15b1ca9ba8229c8e5563cc4c4cf9ad94203a0072dd9",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8156: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 34, \"unit_price\": 74.86, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 79.31, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 24.62, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 17, \"unit_price\": 61.06, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 4, \"unit_price\": 48.73, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 73.41, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7733,
7 + "document_hash": "386fcaff7daca426267d33af6f30657f21e4863b66d5a71d38d0b78a334eb069",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00126_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00126_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-1488: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 25, \"unit_price\": 14.21, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 40.29, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 39, \"unit_price\": 66.39, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 5, \"unit_price\": 58.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 29, \"unit_price\": 35.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 28, \"unit_price\": 51.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 2)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 7944,
7 − "document_hash": "a6bed1ca1c6bee001ded092712010d4dc8d3ec10d0d1f85432e8844be28b9359",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-1488: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 25, \"unit_price\": 14.21, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 40.29, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 39, \"unit_price\": 66.39, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 5, \"unit_price\": 58.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 29, \"unit_price\": 35.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 28, \"unit_price\": 51.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7763,
7 + "document_hash": "0729452f4b76415c15bdd0075e98c4db16464515a675ea3d8e3611adb3c8a3e9",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00127_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00127_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4907: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 4.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 32, \"unit_price\": 57.56, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 38, \"unit_price\": 48.4, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 5, \"unit_price\": 7.69, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 4, \"unit_price\": 49.04, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 19, \"unit_price\": 48.89, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 7953,
7 − "document_hash": "01e9b8b715cbfdd0d66c26d571044c18f9a6d9d2c5146b834291716879cf02d2",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4907: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 4.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 32, \"unit_price\": 57.56, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 38, \"unit_price\": 48.4, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 5, \"unit_price\": 7.69, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 4, \"unit_price\": 49.04, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 19, \"unit_price\": 48.89, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7774,
7 + "document_hash": "bb6e6467042a1b7809f3ea38b83ea82e5554ca36b70042023f682efd5bae752a",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00128_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00128_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-7370: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"beta\", \"units\": 26, \"unit_price\": 33.84, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 3, \"unit_price\": 74.94, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 37, \"unit_price\": 29.12, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 5, \"unit_price\": 71.86, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 21, \"unit_price\": 69.23, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 22, \"unit_price\": 38.14, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 − "char_len": 7945,
7 − "document_hash": "e702731f232f4b91d0513add4b301fd1ef0382eee35df22a98cef7eb727fafca",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-7370: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"beta\", \"units\": 26, \"unit_price\": 33.84, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 3, \"unit_price\": 74.94, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 37, \"unit_price\": 29.12, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 5, \"unit_price\": 71.86, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 21, \"unit_price\": 69.23, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 22, \"unit_price\": 38.14, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 + "char_len": 7763,
7 + "document_hash": "ea7fe68afa60ebc43cd0a501c243c72cd3b993bfaef6e389f12308e1967e3471",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00129_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00129_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-2059: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 2 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"delta\", \"units\": 25, \"unit_price\": 31.69, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 37, \"unit_price\": 44.06, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 17, \"unit_price\": 28.44, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 18.96, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 32.1, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 10.85, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 2)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 − "char_len": 7973,
7 − "document_hash": "e508132470ec83c8745c1899d6c954b865130cad33382718fa48d35d6bea0ec8",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-2059: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 2 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"delta\", \"units\": 25, \"unit_price\": 31.69, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 37, \"unit_price\": 44.06, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 17, \"unit_price\": 28.44, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 18.96, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 32.1, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 10.85, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 + "char_len": 7794,
7 + "document_hash": "46f3b799f18b08ee443481845e8695eff10ac2f2b23c2b177eafce3b42e2ea40",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00130_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00130_2000",
3 3 "family": "exec",
4 4 "split": "dev",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-7512: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 24 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 4.14, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 3.41, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 18.56, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 4, \"unit_price\": 23.95, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 18, \"unit_price\": 17.39, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 30, \"unit_price\": 71.95, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 8072,
7 − "document_hash": "c65f14fbcb1d4d0049a6e641be2826817637866851032f95c4cc1943f87ff809",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-7512: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 24 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 4.14, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 3.41, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 18.56, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 4, \"unit_price\": 23.95, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 18, \"unit_price\": 17.39, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 30, \"unit_price\": 71.95, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7893,
7 + "document_hash": "c415053d25119b89bd769d02be02c390efebcd68b992b946ddf043ad29041f86",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00201_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00201_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8684: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"beta\", \"units\": 18, \"unit_price\": 5.04, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 10, \"unit_price\": 15.42, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 54.9, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 39, \"unit_price\": 7.38, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 33, \"unit_price\": 19.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 35, \"unit_price\": 43.47, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 8073,
7 − "document_hash": "876f090ca1801217ec4295964e7d9ce5b46b9fc96b04db7ca463d6cc8ed74978",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8684: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"beta\", \"units\": 18, \"unit_price\": 5.04, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 10, \"unit_price\": 15.42, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 54.9, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 39, \"unit_price\": 7.38, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 33, \"unit_price\": 19.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 35, \"unit_price\": 43.47, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7892,
7 + "document_hash": "065b6c18bbd16f16126924a54946ca4bf95c5863e57b14f33e4c9d88568f8549",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00202_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00202_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-1160: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 14, \"unit_price\": 68.95, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 10, \"unit_price\": 71.74, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 6, \"unit_price\": 31.62, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 32, \"unit_price\": 43.27, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 5, \"unit_price\": 75.21, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 18, \"unit_price\": 76.88, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 7844,
7 − "document_hash": "660fc77600d7958889cef9b34f9c9a1a8c2d96ef38db054d180f225ebe3d4a42",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-1160: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 14, \"unit_price\": 68.95, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 10, \"unit_price\": 71.74, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 6, \"unit_price\": 31.62, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 32, \"unit_price\": 43.27, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 5, \"unit_price\": 75.21, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 18, \"unit_price\": 76.88, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7665,
7 + "document_hash": "ec13194237af7efe7765a21f1d8303ab8ac449271eb48e3395906648c770bab8",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00203_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00203_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-7417: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 22 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 73.68, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 40.46, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 27.47, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 78.27, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 49.3, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 30, \"unit_price\": 53.29, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 − "char_len": 7967,
7 − "document_hash": "f26e049133c3f806d2045fa255ba4e6c2594f5ecbe872414b75faaf52ceb5033",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-7417: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 22 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 73.68, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 40.46, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 21, \"unit_price\": 27.47, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 8, \"unit_price\": 78.27, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 49.3, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 30, \"unit_price\": 53.29, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 + "char_len": 7788,
7 + "document_hash": "39eee37c7ba5fe1b6d8fce9eef4c00e10a33d8ca049d12ae01b9521d4ac60863",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00204_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00204_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-2345: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 17 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 14, \"unit_price\": 22.64, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 40, \"unit_price\": 49.16, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 8, \"unit_price\": 47.27, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 36, \"unit_price\": 38.71, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 29.38, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 26, \"unit_price\": 22.23, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 8100,
7 − "document_hash": "7cc296695d97fdf8fb07de5772744af9c3a79a52f20ee1e3410187cac4dd94b2",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-2345: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 17 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 14, \"unit_price\": 22.64, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 40, \"unit_price\": 49.16, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 8, \"unit_price\": 47.27, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 36, \"unit_price\": 38.71, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 29.38, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 26, \"unit_price\": 22.23, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7921,
7 + "document_hash": "0aaf1a095160aa21c4485db3b1b171e86d9d41b904ac2a2ea102cc13df19cd22",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00205_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00205_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-9090: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 11, \"unit_price\": 21.72, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 4, \"unit_price\": 33.96, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 7, \"unit_price\": 20.98, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 40, \"unit_price\": 24.33, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 29.74, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 1, \"unit_price\": 9.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 8061,
7 − "document_hash": "1f9b534774ca095126415c70bc29f4400d55f083ec020a658e6ee1263a76072f",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-9090: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 11, \"unit_price\": 21.72, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 4, \"unit_price\": 33.96, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 7, \"unit_price\": 20.98, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 40, \"unit_price\": 24.33, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 29.74, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 1, \"unit_price\": 9.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7882,
7 + "document_hash": "c82f149ddbd77be80773d103825621fb187f06bb60d4fd570c73c2b3cd898ecb",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00206_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00206_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-1049: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 27, \"unit_price\": 41.55, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 10.75, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 79.56, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 5, \"unit_price\": 44.39, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 5, \"unit_price\": 12.61, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 35.76, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 − "char_len": 7908,
7 − "document_hash": "71e5bf98eb246c53babd99cdd8ec1212e594a1af3ddd2a6da69bac721ad65ddd",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-1049: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 27, \"unit_price\": 41.55, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 10.75, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 79.56, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 5, \"unit_price\": 44.39, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 5, \"unit_price\": 12.61, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 35.76, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 + "char_len": 7727,
7 + "document_hash": "e391c9d757bc03677c664222c3ff3f1bbab881d7f566c0072b184e0b90503339",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00207_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00207_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-3534: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 9 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 61.97, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 57.71, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 20, \"unit_price\": 30.35, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 25.39, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 32, \"unit_price\": 54.7, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 66.46, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 2)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 − "char_len": 8035,
7 − "document_hash": "2273befa734c54f0d780db1126ec3ce69ce8f9f829e57586a614786258681ba3",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-3534: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 9 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 61.97, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 57.71, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 20, \"unit_price\": 30.35, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 26, \"unit_price\": 25.39, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 32, \"unit_price\": 54.7, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 66.46, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 + "char_len": 7856,
7 + "document_hash": "7d024469b5d38776a899aa870f5af7e146953a19f1adc1d91f634cda62aa4c14",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00208_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00208_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-9673: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 33, \"unit_price\": 34.08, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 10, \"unit_price\": 62.88, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 9}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 27, \"unit_price\": 63.49, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 23.2, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 78.55, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 32, \"unit_price\": 71.98, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 1)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 − "char_len": 8036,
7 − "document_hash": "e22e990c3c20d7feee2f70e993961e465ac68d3a867c3547dc0566739847c2d8",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-9673: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 33, \"unit_price\": 34.08, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 10, \"unit_price\": 62.88, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 9}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 27, \"unit_price\": 63.49, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 23.2, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 35, \"unit_price\": 78.55, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 32, \"unit_price\": 71.98, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 + "char_len": 7854,
7 + "document_hash": "8528b3fafcf58b9daa88ffa9d7b9b25fb6e225f9bb767849744c05510a5ace37",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00209_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00209_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-2760: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 18, \"unit_price\": 42.3, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 23, \"unit_price\": 72.91, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 38, \"unit_price\": 23.31, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 3, \"unit_price\": 63.77, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 17, \"unit_price\": 32.46, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 52.71, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 1)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 8044,
7 − "document_hash": "bd895760d266f605848302775beaceb129633108ddc74dcbe83a8642eecb0ea3",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-2760: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 18, \"unit_price\": 42.3, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 23, \"unit_price\": 72.91, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 38, \"unit_price\": 23.31, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 3, \"unit_price\": 63.77, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 17, \"unit_price\": 32.46, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 52.71, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7865,
7 + "document_hash": "27a0f4409b3611173adf72865b52c6beef014bce0282fd0498be50deeed192c9",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00210_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00210_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6939: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 15, \"unit_price\": 64.15, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 76.61, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 77.13, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 33.33, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 77.57, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 37, \"unit_price\": 19.87, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 2)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 7990,
7 − "document_hash": "2678fb8184c3c22ce8bfa861af1a68ef2704dd84cb88718d63c1b668adaf1f69",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6939: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 5 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 15, \"unit_price\": 64.15, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 26, \"unit_price\": 76.61, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 77.13, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 28, \"unit_price\": 33.33, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 77.57, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 37, \"unit_price\": 19.87, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}]\n\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7811,
7 + "document_hash": "ffa82307f9b4986f3fc473b8b7df1e4f8f0e1c25d3b6e36cdcf4114a763427c5",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00211_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00211_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6353: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 44.73, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 18.17, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 32, \"unit_price\": 19.62, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 34, \"unit_price\": 61.32, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 11, \"unit_price\": 64.95, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 8, \"unit_price\": 15.18, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 8091,
7 − "document_hash": "5ad4fd06e4149025eddafab6fbf5c707e06c1f7e47f3cbaec839f52cd6744e38",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6353: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 44.73, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 18.17, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 32, \"unit_price\": 19.62, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 34, \"unit_price\": 61.32, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 11, \"unit_price\": 64.95, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 8, \"unit_price\": 15.18, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7909,
7 + "document_hash": "95faa51b0302db54273e9b4469b6eae92c251463238fdad494d437435c293548",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00212_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00212_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8815: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"delta\", \"units\": 36, \"unit_price\": 38.87, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 39, \"unit_price\": 5.47, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 68.81, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 5, \"unit_price\": 31.92, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 68.1, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 17.46, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 8061,
7 − "document_hash": "8a171bf76e4dc9c8921e9b2a4370fc5385ceb9695d62d19fc693110c84df06f0",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8815: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"delta\", \"units\": 36, \"unit_price\": 38.87, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 39, \"unit_price\": 5.47, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 68.81, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 5, \"unit_price\": 31.92, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 68.1, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 22, \"unit_price\": 17.46, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7882,
7 + "document_hash": "2be5dc8496484a99fc11a00be474f4f7f139a8f491a2ebf3fff0db8e7804dd82",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00213_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00213_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-9971: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 26 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 6.93, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 40, \"unit_price\": 72.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 23, \"unit_price\": 79.31, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 19, \"unit_price\": 20.15, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 36, \"unit_price\": 16.11, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 35, \"unit_price\": 59.43, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 10}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 − "char_len": 7876,
7 − "document_hash": "55fc33fe81ccfe25e3ebdcdb70ee135b990fcf94d02bfb56e0116982ffd6df6f",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-9971: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 26 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 21, \"unit_price\": 6.93, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 40, \"unit_price\": 72.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 23, \"unit_price\": 79.31, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 19, \"unit_price\": 20.15, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 36, \"unit_price\": 16.11, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 35, \"unit_price\": 59.43, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 10}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 + "char_len": 7695,
7 + "document_hash": "3c65c42333c25f1f3f90331747f08fafce263c8faa11a56d3a68bc58b2217327",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00214_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00214_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6115: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 20, \"unit_price\": 62.71, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 20, \"unit_price\": 4.15, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 37.58, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 35, \"unit_price\": 54.43, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 24.23, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 14, \"unit_price\": 46.97, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 7997,
7 − "document_hash": "0be81f6d80f5eb03ba862cbc94c8bf20b6ab1196483c947401585e7178fd458d",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6115: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 20, \"unit_price\": 62.71, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 20, \"unit_price\": 4.15, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 20, \"unit_price\": 37.58, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 35, \"unit_price\": 54.43, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 24.23, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 14, \"unit_price\": 46.97, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7815,
7 + "document_hash": "ac0a3ee69ec7da626616f6ffb5e443a4f26a3d7857caaa20f1d4ebfa5355d28b",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00215_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00215_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-9778: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 33.86, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 2.58, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 10, \"unit_price\": 34.09, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 66.24, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 32.36, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 25, \"unit_price\": 39.54, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.",
6 − "char_len": 8073,
7 − "document_hash": "37b95a047621c2a78beaff095b27647064c994bf6ede6ef6b3e91f8296b70eff",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-9778: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 6 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 2 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 33.86, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 2.58, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 10, \"unit_price\": 34.09, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 66.24, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 32.36, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 25, \"unit_price\": 39.54, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 2:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.",
6 + "char_len": 7894,
7 + "document_hash": "a4094c70181359b8442ead384be9497e3fb0c46a4d9266cce07ca77bd9e26e2b",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00216_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00216_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-5343: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 9 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 30, \"unit_price\": 19.57, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 3, \"unit_price\": 57.35, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 18, \"unit_price\": 56.48, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 70.24, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 66.63, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 33.67, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 2)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 8017,
7 − "document_hash": "1deddf301b0b2291cb9bdc4213848eceb17ece12032a2e454bcceb4ca4174397",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-5343: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 9 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 30, \"unit_price\": 19.57, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 3, \"unit_price\": 57.35, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 18, \"unit_price\": 56.48, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 70.24, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 66.63, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 35, \"unit_price\": 33.67, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7838,
7 + "document_hash": "1a218de32e6fe4bbe97927ea16330bda3b598ed66c1517824d94ff90f944e802",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00217_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00217_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-1928: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 20 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 22, \"unit_price\": 71.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 23.77, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 22, \"unit_price\": 39.11, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 38, \"unit_price\": 40.72, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 6, \"unit_price\": 36.45, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 51.53, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 7946,
7 − "document_hash": "7f71cb12d994e6fe2646a0f7b337c441f923868ec6b21c29533122fda4d87a73",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-1928: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 20 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 22, \"unit_price\": 71.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 23.77, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 22, \"unit_price\": 39.11, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 38, \"unit_price\": 40.72, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 6, \"unit_price\": 36.45, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"epsilon\", \"units\": 12, \"unit_price\": 51.53, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7764,
7 + "document_hash": "1223c7391b1da1aeae2d242c0e41de4639218cfe0c90ba9065f1cce42f0eedbd",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00218_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00218_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6421: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 22 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 3, \"unit_price\": 69.57, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 11, \"unit_price\": 53.59, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 16, \"unit_price\": 77.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 24, \"unit_price\": 22.35, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 79.4, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 38, \"unit_price\": 20.83, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 7955,
7 − "document_hash": "2a77fd38142317b7e8868dfcaebb42248ddd462e9339268378a26e4b587eab3d",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6421: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 22 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 3, \"unit_price\": 69.57, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 11, \"unit_price\": 53.59, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 16, \"unit_price\": 77.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 24, \"unit_price\": 22.35, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 79.4, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 38, \"unit_price\": 20.83, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7776,
7 + "document_hash": "971d94c4e7b4ae02142ffb6eb92af9d2cc0f6e4d52e94a64c5132b510197ce8a",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00219_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00219_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-1173: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 9 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 34, \"unit_price\": 79.78, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 39, \"unit_price\": 77.53, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 12, \"unit_price\": 27.42, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 6.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 21, \"unit_price\": 50.95, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 10, \"unit_price\": 13.89, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 8119,
7 − "document_hash": "501d502ac1cd6920ddaeccbc4f0c925ddf4ca966cfb601ffd9d0547d97a741ed",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-1173: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 9 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 34, \"unit_price\": 79.78, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 39, \"unit_price\": 77.53, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 12, \"unit_price\": 27.42, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 6.47, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 21, \"unit_price\": 50.95, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 10, \"unit_price\": 13.89, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7938,
7 + "document_hash": "390edd848add1a4cf011660e8ac9a6a6aa381c4508a8f68635f3217ce20979cb",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00220_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00220_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6509: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 16, \"unit_price\": 67.65, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 4, \"unit_price\": 37.2, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 44.3, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 39, \"unit_price\": 27.9, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 28, \"unit_price\": 7.8, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 61.13, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 1)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 7931,
7 − "document_hash": "a7487c2eb12039fcc44c64460641febdd19eaf0e13d8b6b8f00d018ca564a8b6",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6509: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 19 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"beta\", \"units\": 16, \"unit_price\": 67.65, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 4, \"unit_price\": 37.2, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 31, \"unit_price\": 44.3, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 39, \"unit_price\": 27.9, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 28, \"unit_price\": 7.8, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 33, \"unit_price\": 61.13, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}]\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7750,
7 + "document_hash": "31eca9e7afc70ac5a795edc1d1529c531e0d028342802a61f4496c013e13bf45",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00221_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00221_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8588: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 1 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 12, \"unit_price\": 67.75, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 24, \"unit_price\": 38.86, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 8}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 52.88, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 12, \"unit_price\": 29.86, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 7.64, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 39, \"unit_price\": 27.73, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 7820,
7 − "document_hash": "a986eec8e76aa658fd694272657b8e201d940be0671e7769a934ffe76ca4748a",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8588: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 1 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 12, \"unit_price\": 67.75, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 24, \"unit_price\": 38.86, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 8}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 29, \"unit_price\": 52.88, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 12, \"unit_price\": 29.86, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 36, \"unit_price\": 7.64, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 39, \"unit_price\": 27.73, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 9}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7638,
7 + "document_hash": "e228dfaa0d04173ee28b43513e5fc06914edf5d0c02b09bf0fc534531a583669",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00222_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00222_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4818: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 32, \"unit_price\": 13.55, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 29, \"unit_price\": 25.72, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 19.2, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 79.51, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 42.07, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 57.83, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 9}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 8057,
7 − "document_hash": "fa31c738b8b80170524adedf048965eb739a7ebf7de9fcd4f4192d331dcc3346",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4818: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 21 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 32, \"unit_price\": 13.55, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 29, \"unit_price\": 25.72, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 19.2, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 6, \"unit_price\": 79.51, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 42.07, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 57.83, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 9}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7878,
7 + "document_hash": "040260f25a42680fcc038386368506adaa004bc2592e75e3fbb5903b54cc19ab",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00223_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00223_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4982: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 10, \"unit_price\": 19.44, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 25, \"unit_price\": 15.63, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 37, \"unit_price\": 51.74, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 24, \"unit_price\": 11.86, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 22, \"unit_price\": 33.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 29, \"unit_price\": 44.89, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 7992,
7 − "document_hash": "9b2d718a88e7b451a6e6d433e81fa6c3862777588f40791fe888b2d7a44efa42",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4982: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 10, \"unit_price\": 19.44, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 25, \"unit_price\": 15.63, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 37, \"unit_price\": 51.74, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 24, \"unit_price\": 11.86, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 22, \"unit_price\": 33.09, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 29, \"unit_price\": 44.89, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 1}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7813,
7 + "document_hash": "7eef13486249d89cf05bda367ea9dae2ce2479b2236c1917b2f067c49a981619",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00224_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00224_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-2924: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 15 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 40.1, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 74.89, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 5, \"unit_price\": 67.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 44.81, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 79.23, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 12, \"unit_price\": 60.0, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 7921,
7 − "document_hash": "526a53c484a99dde8d83b8fc83d103060128d6331659920d7688b8836de1ec53",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-2924: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 15 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 40.1, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 10, \"unit_price\": 74.89, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 5, \"unit_price\": 67.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 24, \"unit_price\": 44.81, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 12}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 9, \"unit_price\": 79.23, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 12, \"unit_price\": 60.0, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 7}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7739,
7 + "document_hash": "3e642abb57841365b827053f2437a250dcb419539389820bac778d4596c064fd",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00225_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00225_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-3204: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 34, \"unit_price\": 5.3, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 23, \"unit_price\": 25.28, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 38, \"unit_price\": 22.38, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 3, \"unit_price\": 5.01, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 19, \"unit_price\": 70.26, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 8, \"unit_price\": 5.79, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 7998,
7 − "document_hash": "0d5d08bcef45a939605c15cb0d0b5b1ac3c2304c8358dae05fa7da75db07621f",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-3204: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 7 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 34, \"unit_price\": 5.3, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 23, \"unit_price\": 25.28, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 38, \"unit_price\": 22.38, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 3, \"unit_price\": 5.01, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 19, \"unit_price\": 70.26, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 8, \"unit_price\": 5.79, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7819,
7 + "document_hash": "54918c16a4ae3706a87d182112fca2a39c82c77e3a60fd25a8b47b958f2a6b21",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00226_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00226_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-9781: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 8 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 13.55, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 23, \"unit_price\": 77.55, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 40.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 36, \"unit_price\": 65.14, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 8, \"unit_price\": 43.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 26, \"unit_price\": 50.69, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 7972,
7 − "document_hash": "32ca9297d301e1956917680ad370eda2add0304f9742c49a2023cfa3f2a82bd2",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-9781: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 8 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 13.55, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 23, \"unit_price\": 77.55, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 24, \"unit_price\": 40.4, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 36, \"unit_price\": 65.14, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 8, \"unit_price\": 43.47, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 26, \"unit_price\": 50.69, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7793,
7 + "document_hash": "7a73067df93b17aba1a608bce48f7a6ff16d480af8d23713ec889405f279fc7d",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00227_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00227_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4863: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 30, \"unit_price\": 60.69, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 16, \"unit_price\": 74.12, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 38, \"unit_price\": 66.15, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 8, \"unit_price\": 49.85, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 14.6, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 54.41, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 − "char_len": 8074,
7 − "document_hash": "0297d0253d8ecb7ba91156d4221aff1d54ba5efaed7fe7664734e63d44d31bd0",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4863: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 30, \"unit_price\": 60.69, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 16, \"unit_price\": 74.12, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 38, \"unit_price\": 66.15, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 8, \"unit_price\": 49.85, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Centre\", \"product\": \"beta\", \"units\": 6, \"unit_price\": 14.6, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 1, \"unit_price\": 54.41, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 9}]\n\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.",
6 + "char_len": 7895,
7 + "document_hash": "6afe19e10d57be0082db797187045b004680fa22a13a56a7b8f7e2a51b40597d",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00228_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00228_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-3241: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 24 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 5 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 76.99, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 29, \"unit_price\": 33.94, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 2}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 14, \"unit_price\": 14.45, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 4.57, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 17, \"unit_price\": 52.45, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 19, \"unit_price\": 77.48, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 11}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 7994,
7 − "document_hash": "7bd8eb7ac7409f89d5f44f1f5001fd0660aece03d12d92588e821c86e0d1f69b",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-3241: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 24 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 76.99, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Centre\", \"product\": \"epsilon\", \"units\": 29, \"unit_price\": 33.94, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 2}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 14, \"unit_price\": 14.45, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 6, \"unit_price\": 4.57, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 17, \"unit_price\": 52.45, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 19, \"unit_price\": 77.48, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 11}]\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7815,
7 + "document_hash": "08d5c40fa24cccbcccaac14d408c241ab602604a712b727f12f570eb56887a74",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00229_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00229_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-2051: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 24, \"unit_price\": 76.49, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 13.36, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 78.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 25, \"unit_price\": 41.6, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 23, \"unit_price\": 3.62, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 27, \"unit_price\": 31.65, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 − "char_len": 7905,
7 − "document_hash": "488c5efd60f8e64b88269226071b8befe058a5e2442b99934157b38f5fc41a19",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-2051: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 12 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 24, \"unit_price\": 76.49, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 13.36, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 78.0, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 25, \"unit_price\": 41.6, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 23, \"unit_price\": 3.62, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 27, \"unit_price\": 31.65, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 6}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 + "char_len": 7723,
7 + "document_hash": "b6a34443a51bb95703036fc2467d0c50ad248f99f3c11c0a35d6bc7fcf0ad481",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00230_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00230_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-9897: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 24 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 39, \"unit_price\": 34.41, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 12, \"unit_price\": 36.88, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 33, \"unit_price\": 42.84, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 25.91, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 12, \"unit_price\": 20.67, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 40, \"unit_price\": 69.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.",
6 − "char_len": 8012,
7 − "document_hash": "2e09e5c09991cb1b7c5c288b9a49bb058042a17dc7fd32cde98e2b705477598c",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-9897: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 24 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 39, \"unit_price\": 34.41, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 12, \"unit_price\": 36.88, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 33, \"unit_price\": 42.84, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 1}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 20, \"unit_price\": 25.91, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 12, \"unit_price\": 20.67, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 40, \"unit_price\": 69.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.",
6 + "char_len": 7830,
7 + "document_hash": "cbb9dba4a75d2570390205536d928042eae0341c49e7dcc11a2cea988c175ba9",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00231_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00231_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8917: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 34, \"unit_price\": 42.27, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 21, \"unit_price\": 66.28, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 37, \"unit_price\": 77.97, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 28, \"unit_price\": 73.35, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 48.71, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 4.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 8077,
7 − "document_hash": "9071b939e284c02834a84c70b2af1783b2a26d6217aa2184b3224f0c27400eaf",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8917: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 34, \"unit_price\": 42.27, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 21, \"unit_price\": 66.28, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 37, \"unit_price\": 77.97, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 28, \"unit_price\": 73.35, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"gamma\", \"units\": 18, \"unit_price\": 48.71, \"discount_pct\": 15, \"returned\": true, \"shipped_days\": 7}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 16, \"unit_price\": 4.12, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 1}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7895,
7 + "document_hash": "b599ec4f6ea744baef17b36d05ab828f105675eeebf81a780befd49f389ec9d3",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00232_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00232_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-8049: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 28, \"unit_price\": 25.31, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 3, \"unit_price\": 75.72, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 65.33, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 7, \"unit_price\": 59.04, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 11, \"unit_price\": 48.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 30.99, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 2)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 7990,
7 − "document_hash": "6bb55261f58b559a6304971baddf54cabc7de9843d30afe350a659e21fa02b73",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-8049: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 27 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"alpha\", \"units\": 28, \"unit_price\": 25.31, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 3, \"unit_price\": 75.72, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 65.33, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 7, \"unit_price\": 59.04, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 11, \"unit_price\": 48.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 13, \"unit_price\": 30.99, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7811,
7 + "document_hash": "94e54bf28dac5a404fdf94451d3e632c18f63dff001cc758f89f5239d27f659b",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00233_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00233_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-6605: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 40.36, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 16, \"unit_price\": 13.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 1, \"unit_price\": 30.93, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 77.63, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 12, \"unit_price\": 21.67, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 9, \"unit_price\": 7.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 − "char_len": 7909,
7 − "document_hash": "f88eb8610ee0ae9a0cc4c953e6f302bceb7e6a9f131c2e5f775a4026d048e997",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-6605: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 18 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Est\", \"product\": \"zeta\", \"units\": 31, \"unit_price\": 40.36, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 16, \"unit_price\": 13.05, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 1, \"unit_price\": 30.93, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 77.63, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 12, \"unit_price\": 21.67, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"zeta\", \"units\": 9, \"unit_price\": 7.88, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 6}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.",
6 + "char_len": 7730,
7 + "document_hash": "c0f56e7b9b73df623955c8b6822884e4b53df031c58736213f498ed2b4d693dc",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00234_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00234_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-3367: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 37, \"unit_price\": 64.03, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 30, \"unit_price\": 43.38, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 31.73, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 28, \"unit_price\": 16.65, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 40.15, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 17, \"unit_price\": 33.7, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 1)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 8006,
7 − "document_hash": "89b49129e4581b4b424c4986c040ee62a62ff6f482d53151d96cbcf944c97e02",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-3367: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 28 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Ouest'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 37, \"unit_price\": 64.03, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 30, \"unit_price\": 43.38, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Ouest\", \"product\": \"gamma\", \"units\": 13, \"unit_price\": 31.73, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Ouest\", \"product\": \"beta\", \"units\": 28, \"unit_price\": 16.65, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 7}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 29, \"unit_price\": 40.15, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 17, \"unit_price\": 33.7, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7827,
7 + "document_hash": "3522724b66617b60e55fa67efc23998ff528130352e7a960ee1e052d697670a5",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00235_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00235_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-2404: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 16 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 21, \"unit_price\": 57.5, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 21, \"unit_price\": 43.44, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 19, \"unit_price\": 70.07, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 13, \"unit_price\": 4.78, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 31, \"unit_price\": 3.2, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 1, \"unit_price\": 74.62, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 − "char_len": 8079,
7 − "document_hash": "7870795b3e6c98bee59eb42d0e036ccc1d88fe696a6e7c94016c77fb0f3cefe4",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-2404: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 16 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"zeta\", \"units\": 21, \"unit_price\": 57.5, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"delta\", \"units\": 21, \"unit_price\": 43.44, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 19, \"unit_price\": 70.07, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 9}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 13, \"unit_price\": 4.78, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 31, \"unit_price\": 3.2, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Sud\", \"product\": \"beta\", \"units\": 1, \"unit_price\": 74.62, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 5}]\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.",
6 + "char_len": 7900,
7 + "document_hash": "20bfca2f1ed7277720116b37988eb2bf9331505c61f7491ff7f131ed0b2d70e1",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00236_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00236_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4238: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 7 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 9.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 23, \"unit_price\": 35.91, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 27, \"unit_price\": 13.03, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 55.74, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 15, \"unit_price\": 26.26, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 23, \"unit_price\": 20.92, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 15, \"unit_price\": 33.87, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 9.975 / 100.0)\n return round(total, 2)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 − "char_len": 8048,
7 − "document_hash": "dabe94079fad1aa1fef7653ff5583522be249aa0c33c58334ae1d261091d83f9",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4238: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 9.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 23, \"unit_price\": 35.91, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"zeta\", \"units\": 27, \"unit_price\": 13.03, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Centre\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 55.74, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 15, \"unit_price\": 26.26, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 12}, {\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 23, \"unit_price\": 20.92, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 11}, {\"region\": \"Centre\", \"product\": \"gamma\", \"units\": 15, \"unit_price\": 33.87, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.",
6 + "char_len": 7867,
7 + "document_hash": "23053422d45849043d9eb3706daf105a581cd66b69e96220ab1285c7c92b2058",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00237_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00237_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-5627: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 9 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 37, \"unit_price\": 64.21, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 13, \"unit_price\": 78.67, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 19, \"unit_price\": 39.59, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 18, \"unit_price\": 23.76, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 20, \"unit_price\": 26.17, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 31.81, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 − "char_len": 8024,
7 − "document_hash": "455d86e6a8f1e9be0eaebb2e2ab279c0439c6768273a410e7994bc6a76dfbecf",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-5627: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 11 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 37, \"unit_price\": 64.21, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 5}, {\"region\": \"Ouest\", \"product\": \"zeta\", \"units\": 13, \"unit_price\": 78.67, \"discount_pct\": 0, \"returned\": true, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 19, \"unit_price\": 39.59, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"epsilon\", \"units\": 18, \"unit_price\": 23.76, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Est\", \"product\": \"delta\", \"units\": 20, \"unit_price\": 26.17, \"discount_pct\": 25, \"returned\": true, \"shipped_days\": 14}, {\"region\": \"Nord\", \"product\": \"beta\", \"units\": 19, \"unit_price\": 31.81, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 3}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.",
6 + "char_len": 7842,
7 + "document_hash": "a8320d4e9d153e4398af56ca92c73f39bb1c1b9e97609e9ec096c1157cebe872",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00238_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00238_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-3671: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 1 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 12, \"unit_price\": 46.52, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 31, \"unit_price\": 14.59, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 39, \"unit_price\": 18.43, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 8, \"unit_price\": 15.63, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 25, \"unit_price\": 74.62, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 22.36, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 11}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 0)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 − "char_len": 7855,
7 − "document_hash": "ffdd32b5c64c4cab201265cf785b962e0e60f2f65cf46cfd2674256d0a97fe14",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-3671: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 1 June 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Nord\", \"product\": \"gamma\", \"units\": 12, \"unit_price\": 46.52, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Ouest\", \"product\": \"epsilon\", \"units\": 31, \"unit_price\": 14.59, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 39, \"unit_price\": 18.43, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"epsilon\", \"units\": 8, \"unit_price\": 15.63, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 1}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 25, \"unit_price\": 74.62, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Ouest\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 22.36, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 11}]\n\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 0)\n\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.",
6 + "char_len": 7676,
7 + "document_hash": "068a11a09e40cb07626e21d7abb095fb9c4779acc1a0db602ca10678ae79e3e0",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00239_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00239_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-4265: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 10 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 51.01, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 47.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 14.87, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 37, \"unit_price\": 68.34, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 15.1, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 18, \"unit_price\": 10.35, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 7905,
7 − "document_hash": "1215eafbd18b1d396d2779e2c0227bfcff05e59f1f06d602fc8284f18da6bbc8",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-4265: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 10 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 27, \"unit_price\": 51.01, \"discount_pct\": 5, \"returned\": true, \"shipped_days\": 10}, {\"region\": \"Nord\", \"product\": \"alpha\", \"units\": 32, \"unit_price\": 47.91, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 2}, {\"region\": \"Ouest\", \"product\": \"alpha\", \"units\": 2, \"unit_price\": 14.87, \"discount_pct\": 10, \"returned\": false, \"shipped_days\": 14}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 37, \"unit_price\": 68.34, \"discount_pct\": 10, \"returned\": true, \"shipped_days\": 5}, {\"region\": \"Est\", \"product\": \"zeta\", \"units\": 18, \"unit_price\": 15.1, \"discount_pct\": 15, \"returned\": false, \"shipped_days\": 10}, {\"region\": \"Centre\", \"product\": \"alpha\", \"units\": 18, \"unit_price\": 10.35, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}]\n\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 2)\n\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nDeployment to production requires a reviewer approval and a green pipeline.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7723,
7 + "document_hash": "015c78e1e480fb805976a26912f0308a79a0c4b2122313463b5ff6b5ee996a9b",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/docs/exec/exec_00240_2000.json +3 −3
@@ -2,9 +2,9 @@
2 2 "document_id": "exec_00240_2000",
3 3 "family": "exec",
4 4 "split": "test",
5 − "text": "ENGINEERING TICKET\n\nBug report BR-9289: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 2 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 17, \"unit_price\": 38.92, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 40, \"unit_price\": 28.81, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 23, \"unit_price\": 35.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 30, \"unit_price\": 75.57, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 22.6, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 35, \"unit_price\": 18.22, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct']\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 − "char_len": 7976,
7 − "document_hash": "2598ae3b4041685f7fbf0de4eb4c12a5508a3c374ae89cdf7007d3cf7e6e5924",
5 + "text": "ENGINEERING TICKET\n\nBug report BR-9289: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 2 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.\n\nSample rows (first 6 of the extract):\n[{\"region\": \"Sud\", \"product\": \"alpha\", \"units\": 17, \"unit_price\": 38.92, \"discount_pct\": 5, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 40, \"unit_price\": 28.81, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 8}, {\"region\": \"Est\", \"product\": \"beta\", \"units\": 23, \"unit_price\": 35.65, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Est\", \"product\": \"alpha\", \"units\": 30, \"unit_price\": 75.57, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 13}, {\"region\": \"Sud\", \"product\": \"delta\", \"units\": 15, \"unit_price\": 22.6, \"discount_pct\": 0, \"returned\": false, \"shipped_days\": 4}, {\"region\": \"Sud\", \"product\": \"gamma\", \"units\": 35, \"unit_price\": 18.22, \"discount_pct\": 25, \"returned\": false, \"shipped_days\": 6}]\n\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\n\nThe existing (buggy) implementation is:\n\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n return round(total, 1)\n\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nDeployment to production requires a reviewer approval and a green pipeline.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nCode style follows the repository's formatter settings; do not reformat unrelated lines.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe ticketing system assigns severity on a four-level scale; this ticket is severity 2.\nHistoric tickets BR-1183 and BR-2047 are unrelated and remain closed.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nDeployment to production requires a reviewer approval and a green pipeline.\nAll monetary values are in the client's reporting currency; no FX conversion is applied here.\nUnit tests live in the tests/ directory and are executed in CI on every push.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.\nThe data engineering team refreshes the sales extract nightly at 02:00 local time.\nThe data dictionary defines shipped_days as the number of calendar days from order to shipment.\nDeployment to production requires a reviewer approval and a green pipeline.",
6 + "char_len": 7797,
7 + "document_hash": "4c3927b8378a2b949e85371101d959a0adebcbe41a2d39f239aae883de382e19",
8 8 "questions": [
9 9 {
10 10 "question_id": "q00_exec",
modified data/generated/keys/exec/exec_00001_2000.json +8 −8
@@ -2,13 +2,13 @@
2 2 "document_id": "exec_00001_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "document_hash": "ddfe7fcc3baca3e97144b66188f285a0e8a83018d1ca41b7f37cb80dede62dcc",
5 + "document_hash": "72a702cc7076fb313f97772498675d83532bf6ce59f1d3cbf3bb86fa387dc0e6",
6 6 "questions": [
7 7 {
8 8 "question_id": "q00_exec",
9 9 "qtype": "exec",
10 10 "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences.",
11 − "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Est':\n continue\n if r['units'] < 5:\n continue\n d = r['discount_pct'] + (5 if r['shipped_days'] > 8 else 0)\n d = min(d, 50)\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n",
11 + "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Est':\n continue\n if r['units'] < 5:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n",
12 12 "answer_type": "exec",
13 13 "tolerance": 0.0,
14 14 "supporting_fact_ids": [
@@ -25,9 +25,9 @@
25 25 "attribute": "rules",
26 26 "value": "{\"thr_days\": 8, \"min_units\": 5, \"excl_region\": \"Est\", \"rounding\": 0, \"tax\": 0.0}",
27 27 "kind": "spec",
28 − "sentence": "Bug report BR-7019: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 20 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 5 units; (4) rows shipped in more than 8 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).",
28 + "sentence": "Bug report BR-7019: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 20 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 5 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.",
29 29 "char_start": 20,
30 − "char_end": 751
30 + "char_end": 624
31 31 }
32 32 ],
33 33 "hidden_tests": [
@@ -124,7 +124,7 @@
124 124 "shipped_days": 7
125 125 }
126 126 ],
127 − "expected": 3629.0
127 + "expected": 3711.0
128 128 },
129 129 {
130 130 "input": [
@@ -269,7 +269,7 @@
269 269 "shipped_days": 7
270 270 }
271 271 ],
272 − "expected": 4601.0
272 + "expected": 4683.0
273 273 },
274 274 {
275 275 "input": [
@@ -400,7 +400,7 @@
400 400 "shipped_days": 5
401 401 }
402 402 ],
403 − "expected": 4660.0
403 + "expected": 4778.0
404 404 },
405 405 {
406 406 "input": [
@@ -459,7 +459,7 @@
459 459 "shipped_days": 2
460 460 }
461 461 ],
462 − "expected": 2896.0
462 + "expected": 2962.0
463 463 }
464 464 ]
465 465 }
\ No newline at end of file
modified data/generated/keys/exec/exec_00002_2000.json +9 −9
@@ -2,13 +2,13 @@
2 2 "document_id": "exec_00002_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "document_hash": "7918e3cdcab2a8bfae77558b7b523f4cea70cdc52435393d98d0c7b36de29e60",
5 + "document_hash": "7ec85eb17fda1c57c2a77a31dc79bf35b3c62974f6f1905e409880cbe869b6f5",
6 6 "questions": [
7 7 {
8 8 "question_id": "q00_exec",
9 9 "qtype": "exec",
10 10 "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences.",
11 − "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Nord':\n continue\n if r['units'] < 4:\n continue\n d = r['discount_pct'] + (5 if r['shipped_days'] > 6 else 0)\n d = min(d, 50)\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n",
11 + "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Nord':\n continue\n if r['units'] < 4:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n",
12 12 "answer_type": "exec",
13 13 "tolerance": 0.0,
14 14 "supporting_fact_ids": [
@@ -25,9 +25,9 @@
25 25 "attribute": "rules",
26 26 "value": "{\"thr_days\": 6, \"min_units\": 4, \"excl_region\": \"Nord\", \"rounding\": 0, \"tax\": 14.975}",
27 27 "kind": "spec",
28 − "sentence": "Bug report BR-6302: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 3 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) rows shipped in more than 6 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).",
28 + "sentence": "Bug report BR-6302: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 3 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Nord'; (3) exclude rows with fewer than 4 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.",
29 29 "char_start": 20,
30 − "char_end": 754
30 + "char_end": 627
31 31 }
32 32 ],
33 33 "hidden_tests": [
@@ -124,7 +124,7 @@
124 124 "shipped_days": 3
125 125 }
126 126 ],
127 − "expected": 2969.0
127 + "expected": 3084.0
128 128 },
129 129 {
130 130 "input": [
@@ -165,7 +165,7 @@
165 165 "shipped_days": 11
166 166 }
167 167 ],
168 − "expected": 752.0
168 + "expected": 794.0
169 169 },
170 170 {
171 171 "input": [
@@ -233,7 +233,7 @@
233 233 "shipped_days": 11
234 234 }
235 235 ],
236 − "expected": 2144.0
236 + "expected": 2258.0
237 237 },
238 238 {
239 239 "input": [
@@ -391,7 +391,7 @@
391 391 "shipped_days": 5
392 392 }
393 393 ],
394 − "expected": 8977.0
394 + "expected": 9175.0
395 395 },
396 396 {
397 397 "input": [
@@ -531,7 +531,7 @@
531 531 "shipped_days": 5
532 532 }
533 533 ],
534 − "expected": 7566.0
534 + "expected": 7764.0
535 535 }
536 536 ]
537 537 }
\ No newline at end of file
modified data/generated/keys/exec/exec_00003_2000.json +9 −9
@@ -2,13 +2,13 @@
2 2 "document_id": "exec_00003_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "document_hash": "8ab845867bddfdcb5cf63b1319a6f29794cc9dddea45cd92bca3bc94fe023da7",
5 + "document_hash": "f7d729b32469d142625681408a1dd1aa3d1d99a7c07adb645c9f40d7550e8695",
6 6 "questions": [
7 7 {
8 8 "question_id": "q00_exec",
9 9 "qtype": "exec",
10 10 "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences.",
11 − "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Est':\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct'] + (5 if r['shipped_days'] > 4 else 0)\n d = min(d, 50)\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n",
11 + "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Est':\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n total = total * (1 + 5.0 / 100.0)\n return round(total, 1)\n",
12 12 "answer_type": "exec",
13 13 "tolerance": 0.0,
14 14 "supporting_fact_ids": [
@@ -25,9 +25,9 @@
25 25 "attribute": "rules",
26 26 "value": "{\"thr_days\": 4, \"min_units\": 3, \"excl_region\": \"Est\", \"rounding\": 1, \"tax\": 5.0}",
27 27 "kind": "spec",
28 − "sentence": "Bug report BR-6542: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 5.0 % on the sum; (7) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (4) and rule (2).",
28 + "sentence": "Bug report BR-6542: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 5.0 % on the sum; (6) return the result rounded to 1 decimals (Python round). The current implementation forgets rule (2) and applies no tax.",
29 29 "char_start": 20,
30 − "char_end": 755
30 + "char_end": 628
31 31 }
32 32 ],
33 33 "hidden_tests": [
@@ -115,7 +115,7 @@
115 115 "shipped_days": 13
116 116 }
117 117 ],
118 − "expected": 3222.6
118 + "expected": 3349.8
119 119 },
120 120 {
121 121 "input": [
@@ -228,7 +228,7 @@
228 228 "shipped_days": 13
229 229 }
230 230 ],
231 − "expected": 6782.7
231 + "expected": 7004.7
232 232 },
233 233 {
234 234 "input": [
@@ -269,7 +269,7 @@
269 269 "shipped_days": 13
270 270 }
271 271 ],
272 − "expected": 1236.8
272 + "expected": 1248.8
273 273 },
274 274 {
275 275 "input": [
@@ -391,7 +391,7 @@
391 391 "shipped_days": 13
392 392 }
393 393 ],
394 − "expected": 7525.7
394 + "expected": 7800.7
395 395 },
396 396 {
397 397 "input": [
@@ -486,7 +486,7 @@
486 486 "shipped_days": 14
487 487 }
488 488 ],
489 − "expected": 6066.7
489 + "expected": 6309.5
490 490 }
491 491 ]
492 492 }
\ No newline at end of file
modified data/generated/keys/exec/exec_00004_2000.json +9 −9
@@ -2,13 +2,13 @@
2 2 "document_id": "exec_00004_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "document_hash": "08c5cdfaa7a0742a094ee4726d97a32a89395c354270406bbcf78eff4fdbe8b2",
5 + "document_hash": "aeca575de77be2cf25f1c9f8e053485ad918ef4b3468680a4ef6bfa3b8cb781b",
6 6 "questions": [
7 7 {
8 8 "question_id": "q00_exec",
9 9 "qtype": "exec",
10 10 "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences.",
11 − "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Centre':\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct'] + (5 if r['shipped_days'] > 3 else 0)\n d = min(d, 50)\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n",
11 + "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Centre':\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 2)\n",
12 12 "answer_type": "exec",
13 13 "tolerance": 0.0,
14 14 "supporting_fact_ids": [
@@ -25,9 +25,9 @@
25 25 "attribute": "rules",
26 26 "value": "{\"thr_days\": 3, \"min_units\": 3, \"excl_region\": \"Centre\", \"rounding\": 2, \"tax\": 14.975}",
27 27 "kind": "spec",
28 − "sentence": "Bug report BR-4473: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 22 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (4) and rule (2).",
28 + "sentence": "Bug report BR-4473: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 22 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Centre'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 2 decimals (Python round). The current implementation forgets rule (2) and applies no tax.",
29 29 "char_start": 20,
30 − "char_end": 761
30 + "char_end": 634
31 31 }
32 32 ],
33 33 "hidden_tests": [
@@ -97,7 +97,7 @@
97 97 "shipped_days": 9
98 98 }
99 99 ],
100 − "expected": 5428.38
100 + "expected": 5736.55
101 101 },
102 102 {
103 103 "input": [
@@ -147,7 +147,7 @@
147 147 "shipped_days": 2
148 148 }
149 149 ],
150 − "expected": 6465.92
150 + "expected": 6671.26
151 151 },
152 152 {
153 153 "input": [
@@ -251,7 +251,7 @@
251 251 "shipped_days": 9
252 252 }
253 253 ],
254 − "expected": 10962.43
254 + "expected": 11280.56
255 255 },
256 256 {
257 257 "input": [
@@ -310,7 +310,7 @@
310 310 "shipped_days": 2
311 311 }
312 312 ],
313 − "expected": 5425.82
313 + "expected": 5570.86
314 314 },
315 315 {
316 316 "input": [
@@ -441,7 +441,7 @@
441 441 "shipped_days": 12
442 442 }
443 443 ],
444 − "expected": 9991.84
444 + "expected": 10440.76
445 445 }
446 446 ]
447 447 }
\ No newline at end of file
modified data/generated/keys/exec/exec_00005_2000.json +9 −9
@@ -2,13 +2,13 @@
2 2 "document_id": "exec_00005_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "document_hash": "f885d791d02ed1adb010c9c27804b5c38facf8fd2a09b9b1b6f9cacb7b0acc81",
5 + "document_hash": "c5e26772985f1897f27e3729a56bdf95e08ba4718b928a1480572409c422c83f",
6 6 "questions": [
7 7 {
8 8 "question_id": "q00_exec",
9 9 "qtype": "exec",
10 10 "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences.",
11 − "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Est':\n continue\n if r['units'] < 6:\n continue\n d = r['discount_pct'] + (5 if r['shipped_days'] > 3 else 0)\n d = min(d, 50)\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n",
11 + "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Est':\n continue\n if r['units'] < 6:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n total = total * (1 + 0.0 / 100.0)\n return round(total, 0)\n",
12 12 "answer_type": "exec",
13 13 "tolerance": 0.0,
14 14 "supporting_fact_ids": [
@@ -25,9 +25,9 @@
25 25 "attribute": "rules",
26 26 "value": "{\"thr_days\": 3, \"min_units\": 6, \"excl_region\": \"Est\", \"rounding\": 0, \"tax\": 0.0}",
27 27 "kind": "spec",
28 − "sentence": "Bug report BR-1004: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 6 units; (4) rows shipped in more than 3 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 0.0 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).",
28 + "sentence": "Bug report BR-1004: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 25 March 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Est'; (3) exclude rows with fewer than 6 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 0.0 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.",
29 29 "char_start": 20,
30 − "char_end": 751
30 + "char_end": 624
31 31 }
32 32 ],
33 33 "hidden_tests": [
@@ -196,7 +196,7 @@
196 196 "shipped_days": 5
197 197 }
198 198 ],
199 − "expected": 10831.0
199 + "expected": 11286.0
200 200 },
201 201 {
202 202 "input": [
@@ -354,7 +354,7 @@
354 354 "shipped_days": 11
355 355 }
356 356 ],
357 − "expected": 9939.0
357 + "expected": 10311.0
358 358 },
359 359 {
360 360 "input": [
@@ -413,7 +413,7 @@
413 413 "shipped_days": 8
414 414 }
415 415 ],
416 − "expected": 4721.0
416 + "expected": 4918.0
417 417 },
418 418 {
419 419 "input": [
@@ -598,7 +598,7 @@
598 598 "shipped_days": 10
599 599 }
600 600 ],
601 − "expected": 15203.0
601 + "expected": 15877.0
602 602 },
603 603 {
604 604 "input": [
@@ -675,7 +675,7 @@
675 675 "shipped_days": 5
676 676 }
677 677 ],
678 − "expected": 4292.0
678 + "expected": 4542.0
679 679 }
680 680 ]
681 681 }
\ No newline at end of file
modified data/generated/keys/exec/exec_00006_2000.json +9 −9
@@ -2,13 +2,13 @@
2 2 "document_id": "exec_00006_2000",
3 3 "family": "exec",
4 4 "split": "train",
5 − "document_hash": "2a1bb6d86c77861b166e281bb1deac9a658ed4383a7ade93e9698e33861de0e5",
5 + "document_hash": "283461ef1dfaf2225620026d081a07116ec5fa2173ffa118704c0cf1d53a2eac",
6 6 "questions": [
7 7 {
8 8 "question_id": "q00_exec",
9 9 "qtype": "exec",
10 10 "question": "Rewrite the Python function net_revenue(rows) so that it implements ALL the agreed rules in the ticket. Output only Python code defining net_revenue; no explanations, no markdown fences.",
11 − "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Sud':\n continue\n if r['units'] < 3:\n continue\n d = r['discount_pct'] + (5 if r['shipped_days'] > 4 else 0)\n d = min(d, 50)\n total += r['units'] * r['unit_price'] * (1 - d / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n",
11 + "answer": "\ndef net_revenue(rows):\n total = 0.0\n for r in rows:\n if r['returned']:\n continue\n if r['region'] == 'Sud':\n continue\n if r['units'] < 3:\n continue\n total += r['units'] * r['unit_price'] * (1 - r['discount_pct'] / 100.0)\n total = total * (1 + 14.975 / 100.0)\n return round(total, 0)\n",
12 12 "answer_type": "exec",
13 13 "tolerance": 0.0,
14 14 "supporting_fact_ids": [
@@ -25,9 +25,9 @@
25 25 "attribute": "rules",
26 26 "value": "{\"thr_days\": 4, \"min_units\": 3, \"excl_region\": \"Sud\", \"rounding\": 0, \"tax\": 14.975}",
27 27 "kind": "spec",
28 − "sentence": "Bug report BR-2483: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 23 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) rows shipped in more than 4 days receive an additional 5 percentage points of discount on top of discount_pct, capped at 50 %; (5) line revenue = units * unit_price * (1 - total_discount/100); (6) apply a tax of 14.975 % on the sum; (7) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (4) and rule (2).",
28 + "sentence": "Bug report BR-2483: the function net_revenue(rows) must compute the total net revenue of the rows list (each row is a dict with keys ['region', 'product', 'units', 'unit_price', 'discount_pct', 'returned', 'shipped_days']). Rules agreed with the client on 23 September 2031: (1) exclude returned rows; (2) exclude rows whose region is 'Sud'; (3) exclude rows with fewer than 3 units; (4) line revenue = units * unit_price * (1 - discount_pct/100); (5) apply a tax of 14.975 % on the sum; (6) return the result rounded to 0 decimals (Python round). The current implementation forgets rule (2) and applies no tax.",
29 29 "char_start": 20,
30 − "char_end": 758
30 + "char_end": 631
31 31 }
32 32 ],
33 33 "hidden_tests": [
@@ -169,7 +169,7 @@
169 169 "shipped_days": 4
170 170 }
171 171 ],
172 − "expected": 13971.0
172 + "expected": 14483.0
173 173 },
174 174 {
175 175 "input": [
@@ -291,7 +291,7 @@
291 291 "shipped_days": 3
292 292 }
293 293 ],
294 − "expected": 13520.0
294 + "expected": 14032.0
295 295 },
296 296 {
297 297 "input": [
@@ -422,7 +422,7 @@
422 422 "shipped_days": 10
423 423 }
424 424 ],
425 − "expected": 11047.0
425 + "expected": 11404.0
426 426 },
427 427 {
428 428 "input": [
@@ -526,7 +526,7 @@
526 526 "shipped_days": 13
527 527 }
528 528 ],
529 − "expected": 10526.0
529 + "expected": 11032.0
530 530 },
531 531 {
532 532 "input": [
@@ -621,7 +621,7 @@
621 621 "shipped_days": 4
622 622 }
623 623 ],
624 − "expected": 9516.0
624 + "expected": 9886.0
625 625 }
626 626 ]
627 627 }
\ No newline at end of file
modified data/generated/keys/exec/exec_00007_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00008_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00009_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00010_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00011_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00012_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00013_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00014_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00015_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00016_2000.json +8 −8
Large diff (59 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00017_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00018_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00019_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00020_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00101_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00102_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00103_2000.json +8 −8
Large diff (59 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00104_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00105_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00106_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00107_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00108_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00109_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00110_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00111_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00112_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00113_2000.json +6 −6
Large diff (42 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00114_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00115_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00116_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00117_2000.json +8 −8
Large diff (58 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00118_2000.json +8 −8
Large diff (59 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00119_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00120_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00121_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00122_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00123_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00124_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00125_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00126_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00127_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00128_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00129_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00130_2000.json +8 −8
Large diff (59 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00201_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00202_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00203_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00204_2000.json +8 −8
Large diff (58 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00205_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00206_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00207_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00208_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00209_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00210_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00211_2000.json +8 −8
Large diff (58 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00212_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00213_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00214_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00215_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00216_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00217_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00218_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00219_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00220_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00221_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00222_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00223_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00224_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00225_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00226_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00227_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00228_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00229_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00230_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00231_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00232_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00233_2000.json +8 −8
Large diff (59 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00234_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00235_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00236_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00237_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00238_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00239_2000.json +8 −8
Large diff (59 lines) is not loaded by default to keep the page fast.Load diff
modified data/generated/keys/exec/exec_00240_2000.json +9 −9
Large diff (67 lines) is not loaded by default to keep the page fast.Load diff
modified data/manifests/splits.json +181 −181
Large diff (906 lines) is not loaded by default to keep the page fast.Load diff
added protocol/pilot_matrix.csv +1489 −0
Large diff (1,489 lines) is not loaded by default to keep the page fast.Load diff
added runs/raw/E0_smoke.jsonl +114 −0
Large diff (114 lines) is not loaded by default to keep the page fast.Load diff
added runs/raw/E0_smoke_llama.jsonl +114 −0
Large diff (114 lines) is not loaded by default to keep the page fast.Load diff
added runs/raw/E4_smoke.jsonl +60 −0
Large diff (60 lines) is not loaded by default to keep the page fast.Load diff
added runs/raw/E5_smoke.jsonl +80 −0
Large diff (80 lines) is not loaded by default to keep the page fast.Load diff
added runs/raw/chains/E4_smoke_syn_02000_2000_A4_closed_qwen3b.json +74 −0
Large diff (75 lines) is not loaded by default to keep the page fast.Load diff
added runs/raw/chains/E4_smoke_syn_02000_2000_A5_repairable_qwen3b_llama3b.json +75 −0
Large diff (76 lines) is not loaded by default to keep the page fast.Load diff
added scripts/e6_network.py +76 −0
Large diff (76 lines) is not loaded by default to keep the page fast.Load diff
modified src/wp30/backends/mlx_backend.py +10 −1
Large diff (23 lines) is not loaded by default to keep the page fast.Load diff
added src/wp30/chains.py +159 −0
Large diff (159 lines) is not loaded by default to keep the page fast.Load diff
added src/wp30/cli_extra.py +14 −0
Large diff (14 lines) is not loaded by default to keep the page fast.Load diff
modified src/wp30/data/exec_tasks.py +6 −9
Large diff (33 lines) is not loaded by default to keep the page fast.Load diff
added src/wp30/fanin.py +180 −0
Large diff (180 lines) is not loaded by default to keep the page fast.Load diff
modified src/wp30/runner.py +14 −6
Large diff (46 lines) is not loaded by default to keep the page fast.Load diff
Menu

Theme
↑↓ navigate ↵ open esc close / or ⌘K anywhere