Add an unactivated v2 household prompt contract for issue 165 - #173
Draft
MaxGhenis wants to merge 3 commits into
Draft
Add an unactivated v2 household prompt contract for issue 165#173MaxGhenis wants to merge 3 commits into
MaxGhenis wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Related to #165. This is an unactivated household prompt-contract slice, not
completion of issue 165 or a new benchmark board. The published v1 builder
omits integer inputs and uses a generic disability label. The new, explicitly
opt-in
policybench.prompt_contract_v2renderer exposes supported integer SSDIduration, separate disability gates, and absent/unknown provenance while leaving
the published v1 and board files unchanged.
The renderer freezes the take-up/weekly-hours conventions, labels employer-paid
premiums, preserves numeric precision, rejects incompatible supported values,
and marks unsupported scalar fields without guessing their meaning or units.
It pins version 2.0.0 to the new module's source SHA-256 and a complete rendering
of the existing scenario 074 fixture. It imports no engine or v1 prompt helper,
performs no calculation, and is not imported by an evaluator.
Validation
source/golden identity, program labels, unknown provenance, and invalid inputs.
that refuses network access and actual PolicyEngine package imports.
the exact golden; pytest ran on installed Python 3.14.0.
the fetched base by SHA-256. Existing Vercel settings are preserved.
Scope and gates
Four new paths contain the v2 module, its tests, its golden fixture, and
dedicated documentation. The sole additional change adds an exact-branch
Vercel deployment exclusion to
app/vercel.json. No cost ledger, costschema/reporting, supervisor,
v1 contract, reference, board, or migration file changes are included. Local
contract validation made no model calls, household microsimulations, reference
regeneration, or publication. Normal existing CI is separately authorized.
The new module is a partial fact contract. It does not define requested outputs,
answer schemas, or marital-unit mappings. Unknown values/provenance and
unsupported inputs remain blockers for later evaluation. Suitable data and real
per-fact provenance, engine assumption checks, and the standing reference
sensitivity/exclusion gate remain future work. All existing approvals remain
required. An independent host review of
0c9bbfcfound one P3single-line-validation defect (PB-CONTRACT-001). This head fixes it and adds
10 regression cases; the contract identity/golden header is intentionally
updated and the fixture body is unchanged.
app/vercel.jsondisables automatic deployment only forcodex/issue165-prompt-contract-v2. The live project root isapp. Theconfiguration validates against the official Vercel schema; there are no
matching true rules.
main, the cost branch, and other branches retain thedefault deployment behavior. No remote project settings changed.
All normal hosted checks passed for
94c474f: lint, test, app, and paper.No Vercel deployment was created for the exact branch/head. This draft remains
unactivated and unmerged; all existing review and CI gates remain required.