Skip to content

Bind legacy approvals to authoritative control revisions - #6

Merged
robertdevore merged 1 commit into
mainfrom
codex/revision-bound-legacy-approvals
Oct 13, 2026
Merged

robertdevore merged 1 commit into
mainfrom
codex/revision-bound-legacy-approvals

Conversation

@robertdevore

@robertdevore robertdevore commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

The shipped templates pause at legacy approval gates, but external controllers cannot inspect an authoritative revision or bind a legacy decision to it. inspect --json now includes a bounded control view from the canonical state loader, and legacy resume-decision accepts an optional positive expected_state_revision checked under the run lock before claiming work.

New legacy receipts retain the exact parsed-payload digest. An identical applied decision returns already_applied even after a second gate opens; changed payloads conflict, and claimed/failed or unverifiable historical receipts fail closed for revision-bound callers. Calls without the new field retain historical receipt compatibility. Inspection is observational and does not authenticate actors or authorize execution.

Validation adds UTF-8 size-limit tests and CLI checks for filesystem/SQLite authority, stale and invalid revisions, v2 boundary projection, duplicate/conflicting delivery, uncertain receipts, historical compatibility, second-gate isolation, and completion of all three shipped offline templates without blanket auto-approval. The four control-view tests, complete revision-bound CLI suite (including all three templates), and existing resume-policy suite pass locally on Kujo 1.8.1. Full pinned Kujo 1.6.0 Linux/macOS CI results are pending. The local broad gate was stopped after partial checks because it used different companion revisions and competed with plugin verification; no local full-gate pass is claimed. no release or downstream plugin exposure is included.

@robertdevore
robertdevore merged commit 4c4d34b into main Oct 13, 2026
4 checks passed
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