Skip to content

feat(module): declare bounded installation-only setup methods - #876

Draft
gael-obin wants to merge 1 commit into
codefly-dev:mainfrom
gael-obin:feat/installation-setup-declarations
Draft

gael-obin wants to merge 1 commit into
codefly-dev:mainfrom
gael-obin:feat/installation-setup-declarations

Conversation

@gael-obin

@gael-obin gael-obin commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

A module needs to request bounded installation-only operations without retaining a standing runtime role. Add exact setup method selections to the existing module contract and signed manifest, resolve their requirements from the callee, and refuse optional/self/wildcard or out-of-ceiling selections. Add a per-resource-kind owner-aware declaration so callers do not infer enforcement from role names.

This is a proposed owner extension of the existing Core contract, not a solution-side permission mechanism. It builds on the merged installation declarations in #873 and preserves those fields. The candidate was carried from the existing isolated setup worktree onto main 15e7e12; no running composition was changed.

Validation: fresh go test -count=1 ./contracts/module ./solutionhost passed; diff check passed. Full Core, tagged infrastructure and composed consumer suites were not run. CLI, Authority, Accounts and solution-runtime consumers require matching changes; this parser addition alone does not grant usable setup authority.

Draft: independent architecture review of this head is pending. This belongs to the unfinished installation/durable-review cohort, not the selected upload/extraction demo. The existing candidate Authority dispatcher still has a trusted-host fixture-consent integration blocker; this PR must not be represented as qualification of that cohort. Owner contract acceptance, matching consumer review and release/adoption remain required.

Independent review status

Independent architecture-bouncer review at da5e9b0 is conditional. Matching candidate consumers do not compile with their committed dependency selections, and Records206 does not yet declare the owner-aware enforcement required by Authority for setup. The per-binding union of method scopes also leaves a policy-evolution review question for the contract/Authority owners. Core focused tests passed; this is not a usable published installation cohort.

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