You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A check refuses naming a Role to open pull requests while open_pull_request has no writer (#295's limit, restated) #808
Part of the epic "Epic: slice 1, first approval. A Release on next reviews a pull request to this repo, and the machine user's approval stands" (#182), as a follow-up that gates nothing there. It gates the first Role named to open pull requests.
Why. "Acceptance: a pull request is bound to the issue it serves by its Run or branch, not by its author's closing link" (#295) said the gap the author's link leaves "must not outlive slice 1". The binding by the opening Run's record and by the branch is built and tested, but its writer is not: "Acceptance: a pull request the Factory opens is bound to its issue by the Run that opened it" (#342) waits on the push Effect and harness/push.py, which is slice 2's. The ruling of 2026-11-13 on #182's box 13 (Solution Architect, delegated, with the Factory Builder, on the Maintainer's away approval) lets #342 move to slice 2 only because nothing the binding guards exists yet: no contract is in force, no Role opens a pull request, and config/defaults.json has "open-pull-request": null. It restates #295's limit as "before any Role is named to open pull requests, or any contract is in force", and asks for a check so that the limit is held and not remembered.
Done when
A check refuses a config/defaults.json that names a Role for open-pull-request while the Effect open_pull_request has no writer: no step of the Harness that makes the write and records the Run that opened the pull request. It says which is missing. With the Role null, as today, it passes.
A counter-example under examples/invalid/ that names an opening Role with no writer is refused by it, and a mutant shows the check holds.
config/defaults.json is a model Lens's input and a protected path: if the check needs a change there, that part goes by the Maintainer's hand. The check itself, under tools/, does not.
Activity