Skip to content

feat(approval): record prompt_sha256 on every decision audit line - #18

Merged
readyagentsdev merged 1 commit into
mainfrom
feat/approval-prompt-sha256
Sep 30, 2026
Merged

readyagentsdev merged 1 commit into
mainfrom
feat/approval-prompt-sha256

Conversation

@readyagentsdev

Copy link
Copy Markdown
Owner

Every approval decision audit line (approve and reject, classic and enterprise gates) now carries prompt_sha256, the sha256 of the prompt the decision was made on.

After a reapprove_required refusal the pause is re-baselined to the new prompt, so a re-approval's decision line carries the new digest, not the one on the original paused line.

  • src/readyagents/workflow/nodes.py: prompt_sha256=approval_prompt_digest(prompt) on both decision auditor calls.
  • tests/test_approval_digest.py: first approve, re-approve after mismatch (asserts the new digest and no decision line on the refusal), reject after an edit.
  • docs/workflows.md: re-baseline behaviour and the decision-line field.
  • CHANGELOG Unreleased entry.

Not included: the examples/approval_gate.yaml description tweak. That file is pinned byte-for-byte to v1.9.0 by the *_additive tests, so it's left alone.

Approve and reject decision lines (classic and enterprise gates) carry the
digest of the prompt the decision was made on. After a reapprove_required
refusal the pause is re-baselined, so a re-approval records the new digest.
Documented in docs/workflows.md; CHANGELOG Unreleased.

Signed-off-by: Agent G <326687097+readyagentsdev@users.noreply.github.com>
@readyagentsdev
readyagentsdev merged commit a4d78a4 into main Sep 30, 2026
56 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