Skip to content

fix(projections): resolve portable public project policy - #218

Merged
rldyourmnd merged 2 commits into
mainfrom
fix/released-public-project-owner-resolution-20261006
Oct 6, 2026
Merged

rldyourmnd merged 2 commits into
mainfrom
fix/released-public-project-owner-resolution-20261006

Conversation

@rldyourmnd

@rldyourmnd rldyourmnd commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Released public projects passed the operation eligibility guard but still failed portable compilation because no private estate owner register is included in a public bundle. Read-only generation also retained a module-only guard.

Use an explicit public released-policy compiler path for both generation and plan/apply. Missing owner registers are permitted only at that portable boundary and the existing standalone public-module boundary. Development public projects still require their estate register; corrupt registers, private release targets and unresolved explicit owner selectors remain rejected.

Validation: a complete synthetic immutable archive reproduced both pre-fix failures. Successful public-project operation inputs and read-only generation now pass, without writes. Five compiler boundary tests pass. Full go test ./... and 70 Python tests passed; source projections were regenerated and committed context verification passed.

@rldyourmnd
rldyourmnd merged commit 5de6f93 into main Oct 6, 2026
8 checks passed
@rldyourmnd
rldyourmnd deleted the fix/released-public-project-owner-resolution-20261006 branch October 6, 2026 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant