Sync spec and manifests from microplex core pack#262
Closed
MaxGhenis wants to merge 1 commit into
Closed
Conversation
The working copy of the US pack in microplex core (packs/us at claude/spec-driven-engine) evolved past this repo after #261: resolved ACS housing source-imputation decisions, entity corrections in the variables ledger, an updated source-impute block manifest, and a new arch_targets.json manifest referenced by targets.arch.manifest. Copy those files back so this repo matches core byte-for-byte, and bump the pinned core ref in the content-package gate to 1ee026f (the targets.arch.manifest field postdates the old pin's spec schema). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
|
Closing — wrong direction. Per the consolidation plan (everything in 🤖 Generated with Claude Code |
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
1 participant
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.
What
Re-syncs this content pack with the working copy in
microplexcore (packs/us/atclaude/spec-driven-engine@1ee026f), which had evolved past this repo since #261:specs/us-2024.yaml:rentandreal_estate_taxesresolved fromopen_decisionto declared ACS source-imputation steps; entity corrections for four ledger entries (person→tax_unit/spm_unit, onespm_unit→person);targets.arch.manifestnow points atmanifests/arch_targets.json.manifests/pe_source_impute_blocks.json: ACSdataset_id,pre_subsidy_rentmapping,pension_income, household-head row filters, and group-count columns.manifests/arch_targets.json: new (added in core PRs Require core benchmark family floors for eCPS gates #64–Add matched household thinning methods #65), referenced by the spec..github/workflows/content-package.yml: bump the pinned core ref5a1ea5e→1ee026f— thetargets.arch.manifestfield postdates the old pin, so the old schema would reject the synced spec.Verification
Ran the gate locally against core @
1ee026f:find . -name '*.py'still prints nothing; the pack stays spec-only. After the copy,specs/and all five manifests are byte-identical to core'spacks/us/.Note
This is a mechanical re-sync, not the durable fix. The spec now lives in two repos and they drifted within 48 hours of #261; a single canonical home (or an automated sync check between the two) is the real solution — flagged in the 2026-06-09 architecture review.
🤖 Generated with Claude Code