Generated Model Artifacts
FABLE Pyculator is a wrapper and notebook interface for Modelwright-generated Python models. It ships a reproducibility check for the repaired 2024 workbook, but it does not expose a general workbook-to-model generation API.
That boundary matters when comparing workbook versions. The 2021 workbook should be paired with a 2021 generated Python model. Running a 2021 workbook-derived wrapper against the 2020 generated model can produce plausible-looking tables with the wrong calculation artifact behind them.
Local Artifact Contract
Keep generated models under ignored tmp/ paths:
Workbook version |
Source workbook |
Matching generated model |
|---|---|---|
2020 |
|
|
2021 |
|
|
2024 |
|
|
The 2020 example notebook may materialize the compressed 2020 generated model from a sibling Modelwright checkout. The 2021 and 2024 example notebooks materialize validated compressed generated models tracked in this repository:
examples/fable_2021/generated_fable_2021_model.py.xz
examples/fable_2024/generated_fable_2024_model.py.xz
Those archives are the tracked generated-model exceptions in this repository. Each archive has a
tracked .sha256 sidecar for the uncompressed model:
examples/fable_2021/generated_fable_2021_model.py.sha256
examples/fable_2024/generated_fable_2024_model.py.sha256
The portal hashes the local working model against the sidecar before preparation. A mismatch triggers re-materialization from the tracked archive and is shown explicitly on the Artifacts page. The 2020 artifact has no tracked archive sidecar because it is restored from a sibling Modelwright checkout.
Source workbooks, decompressed generated models, raw generation JSON files, and validation reports
still belong under ignored tmp/ paths.
2024 Regeneration Check
The repaired 2024 workbook can be converted from scratch with Modelwright 0.1.0a9 or newer:
.venv/bin/python scripts/regenerate_fable_2024_model.py
The check writes the regenerated model under ignored
tmp/fable2024-regeneration/, verifies every declared output closes, and compares the result
byte-for-byte with examples/fable_2024/generated_fable_2024_model.py.xz. The current result is
410,299 translated formulas, 10,274 declared outputs, zero output-closure failures, and an exact
archive match. The tracked model’s LAND!AA17:AA27 cells are native generated formulas.
The earlier blocked repro used Modelwright 0.1.0a8. The project now requires
modelwright>=0.1.0a9 so the complete 2024 formula set translates.
To prepare or explicitly run a local 2021 rebuild from the public source workbook, see FABLE FreshForge Rebuild Command. To compare output-ref boundaries before choosing a rebuild target, see Output-Ref Strategy Comparison. To package compact evidence across an explicit output-ref strategy matrix run, see FABLE 2021 Benchmark Matrix Evidence Cookbook.
Spec Discovery Versus Model Generation
The notebook spec helpers discover FABLE-C wrapper metadata:
from fable_pyculator import build_2021_notebook_spec
spec = build_2021_notebook_spec("tmp/private-workbooks/2021_Open_FABLECalculator.xlsx")
This reads workbook structure such as scenario selection controls, scenario-definition tables, output tables, and curated headline series. It does not produce generated calculation source.
The run helpers load an already-generated Python model:
from fable_pyculator import run_2021_notebook_loop
result = run_2021_notebook_loop(
{"gdp_scen": "SSP1"},
workbook_path="tmp/private-workbooks/2021_Open_FABLECalculator.xlsx",
generated_model_path="tmp/generated-models/fable-2021/generated_fable_2021_model.py",
include_figures=False,
)
If the generated model path is missing, restore or create that artifact first. Do not point the
2021 helper at tmp/generated-models/fable-2020/generated_fable_2020_model.py.
About Modelwright JSON Inputs
Modelwright’s low-level generation command expects explicit JSON artifacts:
contract.jsondescribes the generated module boundary: selected inputs, selected outputs, generated symbols, and dependency scope.expressions.jsoncontains translated formula expressions for generated symbols.constants.jsoncontains literal input values or cached constants needed by the generated model.
Those files are Modelwright generation inputs. FABLE Pyculator does not expose a general API that creates them from a FABLE workbook, and it should not silently invent them. The 2024 regeneration script exercises Modelwright’s high-level extraction, translation, inference, and generation APIs directly; the 2021 generated model published here was created by Modelwright during Phase 8 and then compressed for notebook users.
Current Validation Boundary
The 2020 generated model tracked in the sibling Modelwright repository has Modelwright validation evidence. Phase 8 added matching FABLE Pyculator evidence for the public 2021 FABLE-C generated model artifact:
extracted sheets: 62;
extracted cells: 413,776;
formula cells: 297,002;
translated formula cells: 297,002;
comparable cached outputs: 281,922;
generated-output matches: 281,922;
mismatches: 0;
non-comparable cached blank formula outputs: 15,080.
The 2021 claim is limited to the public 2021 FABLE-C workbook and the compressed generated model
artifact in examples/fable_2021/. It is not a claim about arbitrary country calculators,
production readiness, or FABLE-P Canada equivalence.
Compact Evidence Summaries
After running a local Modelwright/FreshForge generated-model workflow, use
scripts/package_fable_validation_evidence.py to summarize restored artifacts under
tmp/generated-models/fable-YYYY/. The command writes compact summaries under
tmp/validation-evidence/fable-YYYY/ and reports incomplete evidence unless explicit comparison
counts are present. See Validation Evidence Packaging.
For manual benchmark orchestration around those artifacts, including extraction-only, FreshForge plan, and explicit FreshForge run modes, use Opt-In Benchmark Evidence Workflow.