PolicyEngine / PolicyEngine/chronicle

Port Thesis official-observation facts (49 rows on codex/thesis-ledger-facts) into source packages

Open
#74 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
1
Avg merge
11h 48m
Merged PRs (30d)
45

Description

What

Port the Thesis official-observation facts from the codex/thesis-ledger-facts branch into proper source packages, now that the schema types assertions (#73).

⚠️ Scope correction (2026-07-02): this is not just PR #52's five May-2026 BLS rows. The branch has kept recording after that PR went stale and is now 49 rows at tip fd612b5, spanning BLS Employment Situation, May CPI/PPI, MTS, weekly claims, BoC and ECB June decisions, UK April GDP, Canada April permits, SNAP QC and Medicaid PI benefits-delivery rates, and the FY2025 SNAP payment error rates that resolved the 2026-06-30 Thesis mass resolution. Do not delete the branch until every row is ported — it is the provenance archive for live Thesis resolutions.

Compatibility is already verified: all 49 rows load under the post-#73 schema with zero validation errors, default to assertion: observation, and keep distinct stable keys.

Shape

One declarative source package per publisher release (news-release HTML or data file as the content-addressed raw artifact, guard cells, full cell lineage), with assertion: observation and first-print vintages (may_2026_first_print). Stable source_record_ids must be preserved exactly — downstream Thesis resolutions reference them.

Notes

  • Publishers revise (BLS payrolls, CPI): each print is its own source-release revision; first print and revisions are distinct facts under the same series, which the release-identity model already handles.
  • The recording workflow that appends to the branch should switch to authoring source packages once this lands.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect the 49 rows on codex/thesis-ledger-facts at tip fd612b5 and the post-#73 schema before locating the source-package examples. Port every row with its raw artifact, guard cells, cell lineage, assertion, first-print vintage, and exact source_record_id; done means all 49 load with zero validation errors and the branch remains available as provenance.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.