SPB Git

spb/wp29_uqo

Public

# Contract — F4-dev-01 (written P0, 2026-10-29)

Question. From the provided plain-text extract of StatCan The Daily "Labour Force Survey, September 2026" only: (a) extract the national seasonally adjusted unemployment rate (%) for Sept 2026 and the monthly change in national SA employment (persons), each with a locator naming the ## ... section heading where it is printed; (b) judge the assertion "core-aged women's unemployment rate rose 0.3 pp to 5.3%, and core-aged men's rate also rose, by 0.2 pp, to 5.8%" as supported / not_supported / not_assessable.

Estimands. Printed values (no recomputation): number as printed; employment change converted "68,000" with sign per text ("declined" -> negative). Verdict: supported only if every element is stated; not_supported if any element is contradicted; not_assessable if quantity absent. Meaningful under the assumption the extract faithfully reproduces the release (README/header state "No numbers were altered").

Outputs. out/results.json keys: unemployment_rate_sep2026 (number), employment_change_sep2026_persons (int), locators (object with both keys), assertion_verdict, assertion_locator, assertion_reason (str), task_id="F4-dev-01", feasibility, feasibility_reason (str|null), data_issues (array of {issue,handling}), n_input_rows ({file: wc -l lines}), n_analysed (int), random_seed (null). Also out/report.md (6 sections), out/analysis.py (regenerates results.json from data/, prints matched source lines), out/claims.json; plus protocol files (state/, exclusions.csv).

Information rules. Extract is the only admissible evidence; no memory of LFS values. Locator format statcan-daily-lfs-2026-09 | section "<heading>". Exact printed values.

Invalidity / impossibility. Figures absent from the extract or contradictory printed values without resolution; using outside knowledge; locator not pointing to a ## heading.

Files · main
Menu

Theme