Skip to content

Completed work closes itself, with its source issue (Pod 0.21.13) - #116

Merged
j3w1 merged 16 commits into
mainfrom
orca/pes-109-completed-closes
Oct 23, 2026
Merged

j3w1 merged 16 commits into
mainfrom
orca/pes-109-completed-closes

Conversation

@j3w1

@j3w1 j3w1 commented Oct 23, 2026

Copy link
Copy Markdown
Owner

Pod 0.21.13 is the closure milestone and part of #109. Completed PES and SEAL work now closes itself, along with its own bound source issue, without any owner step. Work that is not proved complete becomes a task for the project lead.

What changes

  • Delivery proved by GitHub (R153). Evidence closure accepts a merged pull request that GitHub links to the bound source issue as delivery proof when no PR is recorded. The PR must be merged into the bound target, and its repository, base, merge commit and pagination are all checked. Every recorded-PR check stays in force. The source must still be proved by every PoD ticked or the issue closed as completed. Pod never creates a Governor delivery record from this evidence.
  • Governance changed after completion (R154, R158). A closing checkpoint or report keeps the trusted baseline and adopts nothing once completion is proved. That holds for Governor-recorded delivery and for GitHub-linked delivery, including after an Orca runtime change. When no recorded or linked merge exists, the refusal names the project lead's task and asks no owner question. A write that only records a verified delivery is exempt in the same way. Ordinary writes keep their existing governance rules.
  • Closing the source issue (R155). After Pod records a closure, it closes the objective's own bound source issue as completed. It does this only when every recognized PoD line is ticked. It reads the issue fresh immediately before the write, then reads it back afterwards. The step is idempotent, and pod sweep retries it. Pod never mutates a parent SEAL or EEL named only in references; each one is listed as a lead task.
  • Reopened issues (R155). A person reopening an issue after Pod's recorded closure counts as their intent: Pod never closes it again and shows a lead task. Reopens that happened before the work finished do not block closing. Ordinary closures now store closure.at, set once by the closing write, for this check.
  • Claim-only successors (R153). Closing a claim-only successor closes or reports the PES its predecessor binds.
  • SEAL binding (R156). A direct objective may bind its own SEAL issue. For a bound SEAL, - [ ] **ACn lines are recognized alongside PoD#N in ticks, mapping, repair and issue revision. Criteria whose reference is exactly ACn map to those lines.
  • Ticks on a completed source (R157). When a source issue is already closed as completed, Pod reconciles its PoD ticks without asking whether the work is done. Role, source-revision and unknown-write holds still apply.
  • Wording audit (R158). Refusal, status and guidance text no longer tells a caller to ask the owner about closure, PoD ticks or bookkeeping. This includes the record-size refusal, which now names the lossless steps first. Genuine owner decisions remain unchanged: scope, consent, deploy, Defaults and reopen.
  • Tracked test for the #208 case. A 16-receipt assurance consumes a review that was admitted before the upgrade.

Limitations

  • Records written by 0.21.13 cannot be read by 0.21.12: older Pod refuses a record that carries closure.at. Do not roll back below 0.21.13 after it has written closures.
  • When completed work has no recorded or linked merge, its only exit after a governance change is still the owner's. That route belongs to pod#111.

Evidence (separate facts)

  • Implementation: done by supervised workers plus coordinator integration. Worker success is not acceptance.
  • Focused checks at the head: the affected modules pass on Python 3.13 and 3.14. Skill validation, inventory, source audit, the suite-lane check, compile and whitespace also pass.
  • Full local gate: tools/gates.py on the exact head passed on Python 3.13 (503 s) and 3.14 (518 s). Each run had 3218 tests with 0 failures, and all 11 gates passed.
  • Independent review: fresh reviewers worked under the installed 0.21.12 mechanism through three closure rounds, plus a final scoped audit, with records re-checks at each candidate. The final reviews of the head returned ACCEPT, with one advisory left.
  • Hosted CI, merge, install readback and the live closure of PES: Completed work closes itself: renewable rows, larger histories, no owner step #109: not run yet.

🤖 Generated with Claude Code

@j3w1
j3w1 merged commit bbe1785 into main Oct 23, 2026
8 checks passed
@j3w1
j3w1 deleted the orca/pes-109-completed-closes branch October 23, 2026 14:16
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