Skip to content

A check refuses naming a Role to open pull requests while open_pull_request has no writer (#295's limit, restated) #808

Closed

Description

@don-petry

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

Not here: the writer itself (#342), and the window after the last pass that decision 0140 names (#550's, carried to slice 2).

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions