PolicyEngine / PolicyEngine/policyengine.py
Add a versioned execution receipt contract
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 9
- Avg merge
- 15h 51m
- Merged PRs (30d)
- 9
Description
PolicyEngine needs a stable, engine-neutral way to record what a caller requested and what actually executed. This is increasingly important as execution moves across PolicyEngine Core, Axiom, and Populace-backed population artifacts.
Add a strict, versioned execution receipt that:
- separates requested aliases from resolved runtime, model, data, ruleset, and population identities;
- uses cross-language canonical request and result hashes;
- snapshots certified release context without claiming unused components ran; and
- can be bound into offline-verifiable simulation TRACE run records.
The contract should remain JSON round-trippable and suitable for Python, API, and frontend consumers.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by mapping how PolicyEngine Core, Axiom, Populace-backed population artifacts, and simulation TRACE run records currently represent execution context. Define the versioned receipt around requested aliases, resolved identities, canonical hashes, and certified release context. Done means the contract is strict, JSON round-trippable, cross-language, and suitable for offline-verifiable TRACE records without implying unused components ran.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100