PolicyEngine / PolicyEngine/chronicle

Add Ostbelgien family-allowance facts

Open
#218 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

Refs #69.

Source gap

Chronicle has no direct post-2019 German-speaking Community child-benefit
caseload and expenditure package. The official Ostbelgien Statistik page
returns HTTP 403 to automated retrieval in the current environment. Search
snippets and the manual HTML transcription on an unmerged branch are not
publisher artifacts and must not become facts.

Deterministic handoff

Use the Ostbelgien entry in
FETCH-MANIFEST-BELGIUM-PUBLIC-FACTS.json to capture the raw official page
response/source from:

https://ostbelgienstatistik.be/desktopdefault.aspx/tabid-3748/6766_read-39090/

If the values are injected from a separate official endpoint, replace the
handoff with that endpoint and pin its native response rather than saving an
incomplete HTML shell.

Acceptance criteria

  • Pin unchanged publisher response bytes with URL, retrieval details,
    SHA-256, size, page update timestamp, and content-addressed raw-storage
    pointer.
  • Verify the bytes themselves contain exact table labels, periods, units,
    caseload, and expenditure before authoring any facts.
  • Preserve the German-speaking Community scope exactly. Do not use search
    snippets, OCR, screenshots, manual transcription, imputation, or derived
    amounts.
  • Run validate-package, source-cell preservation, fact-load,
    consumer-artifact, raw-facts-boundary, ruff, and git diff --check checks.

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

Start with the Ostbelgien entry in FETCH-MANIFEST-BELGIUM-PUBLIC-FACTS.json and retrieve the official response from the listed URL. Verify the raw bytes contain the required labels, periods, units, caseload, and expenditure before authoring facts. Done means the unchanged response is pinned with provenance and SHA-256, and all listed validation, loading, artifact, ruff, and diff checks pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
json, python
Domain
data, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.