§Australia Labour Force Employment Change, August 2026
Framing and resolver: the registered target is abs.labour.employment_change.australia for August 2026, unit thousands, dataPointId abs.labour.employment_change.australia.august_2026.first_print, and catalog slug abs-labour-employment-change-australia-august-2026. The canonical sourceBinding URL returns ABS employed-person levels in thousands for LF/M3.3.1599.20.AUS.M; this forecast preserves the registered employment-change target and treats the resolving value as the same-release month-over-month difference.
curl -sSL https://www.abs.gov.au/release-calendar/future-releases/202609 and extract the Labour Force, Australia row↳ ABS release calendar excerpt fetched this run: time datetime=2026-09-24T01:30:00Z, displayed as Thursday 24 September 2026 11:30am AEST; product Labour Force, Australia; reference period August 2026.curl -sS 'https://data.api.abs.gov.au/rest/data/LF/M3.3.1599.20.AUS.M?lastNObservations=30&format=jsondata'↳ ABS Data API meta prepared 2026-08-13T17:07:32Z; latest seasonally adjusted employed-person levels in thousands were 2026-02 14721.205316, 2026-03 14741.551774, 2026-04 14702.952844, 2026-05 14746.946935, 2026-06 14823.289454.Parse fetched ABS levels and compute same-vintage month-over-month changes↳ Computed recent changes in thousands from fetched ABS LF/M3.3.1599.20.AUS.M levels: 2026-02 +22.9, 2026-03 +20.3, 2026-04 -38.6, 2026-05 +44.0, 2026-06 +76.3; last 24 changes had mean +20.9, median +32.0, sample sigma 39.7, min -74.8, max +104.0.Compute thesis_model_candidate_v1 compact candidates from fetched changes through 2026-06↳ Model candidates for 2026-08 employment change, train_cutoff 2026-06, calibration_n 24: persistence point +76.3 with 80% interval +25.6 to +127.1; trailing12mean point +21.0 with 80% interval -29.8 to +71.8; last24mean point +20.9 with 80% interval -29.8 to +71.7. Walk-forward calibration over 17 observations: persistence MAE 56.7 RMSE 66.7; trailing12mean MAE 38.9 RMSE 47.8; expandingmean MAE 36.4 RMSE 46.7.curl -sSL -w HTTP_STATUS https://app.thesisinstitute.org/specs.json↳ Slug-check fetch for https://app.thesisinstitute.org/specs.json returned HTTP 404 with an HTML/Next error page; fallback local public generated ledger target contains catalogSlug abs-labour-employment-change-australia-august-2026 and resolutionDate 2026-09-24 for this dataPointId.Base rate / reference class: using the last 24 fetched same-series month-over-month employment changes through June 2026, the distribution is mean +20.9 thousand, median +32.0 thousand, sample sigma 39.7 thousand, range -74.8 to +104.0 thousand. Last-print persistence at +76.3 thousand is a high-side June spike and had materially worse walk-forward error than recent-mean candidates, so I use the trailing/recent-mean model as the outside-view prior.
Prior/update/interval: selected prior = trailing12mean/last24mean blend centered at +21.0 thousand because trailing12mean point +21.0 and last24mean point +20.9 are effectively identical, with no official July print or direct August-specific signal fetched this run to justify a material deviation. Adjustment components: +0.0 thousand current-evidence update, since the June +76.3 spike is already in the fetched history and persistence underperformed in walk-forward tests. Interval method = normal wrapper from last-24 realized change dispersion; sigma = 39.7 thousand, 80% half-width = 1.28*sigma = 1.28*39.7 = 50.8 thousand, so 21.0 - 50.8 = -29.8 and 21.0 + 50.8 = 71.8.
Counter-consideration: upside risk outside the interval would be another broad hiring surge or survey rotation effect that keeps the August same-vintage employment gain above +71.8 thousand; downside risk outside the interval would be payback after June's unusually strong gain, weaker vacancies, or a participation/labour-demand softening that pulls the August change below -29.8 thousand.
Review disposition: accepted the optional clarity suggestion by tightening the resolver discussion around the registered employment-change target and ABS level-series mechanics. Rejected removing the specs.json entry because it was actually fetched during slug checking, even though it returned 404 and was not affirmative source evidence.