Skip to content

Add pattern: Approval-Bound Transactional Write - #160

Merged
nibzard merged 3 commits into
nibzard:mainfrom
Val1-IT:add-approval-bound-transactional-write
Oct 14, 2026
Merged

nibzard merged 3 commits into
nibzard:mainfrom
Val1-IT:add-approval-bound-transactional-write

Conversation

@Val1-IT

@Val1-IT Val1-IT commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

PR intent

  • Adds a reusable, generalized pattern (not a product announcement).
  • One pattern per PR.

Reviewer checklist

  • Problem, Solution, and Trade-offs are clearly documented.
  • No marketing language or calls to action in the PR description or diff content.
  • The pattern is not tied to a single brand as its primary value proposition.
  • Public references are included; if self-referencing, additional context from third-party or non-affiliated sources is provided when available.
  • Conflict-of-interest disclosures are included where applicable.

Notes

Adds patterns/approval-bound-transactional-write.md under Reliability & Eval.

It sits next to human-in-loop-approval-framework but covers a different part: binding the approval to one plan version, checking for drift, and committing the write, the postcondition check and the idempotency key in one transaction, so a resumed or retried run can't apply the change twice.

Conflict of interest: I maintain LedgerGuard, which is listed as one reference and disclosed in both based_on and References. The primary source is Brandur Leach's idempotency-keys write-up. The other references are Will Chan, the Postgres docs, and two public agent-framework issues where this bug shows up. Status is emerging, not anything stronger.

Why I think it's new here: the existing approval and plan patterns stop at "a human said yes". The failure this one handles happens after that: the approved run gets resumed or retried and the write lands twice, or lands on a row that changed after approval. Both linked framework issues are that bug.

External links are github.com, postgresql.org and two independent technical write-ups (brandur.org, willchan.me). No vendor links.

@vercel

vercel Bot commented Oct 8, 2026

Copy link
Copy Markdown

@Val1-IT is attempting to deploy a commit to the nkkko's projects Team on Vercel.

A member of the Team first needs to authorize it.

Val1-IT and others added 3 commits October 15, 2026 00:44
The related front-matter cited human-in-the-loop-approval-framework;
the pattern's slug is human-in-loop-approval-framework.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Rebuild generated aggregates after rebasing onto current main.
bun run build:data output.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@nibzard
nibzard force-pushed the add-approval-bound-transactional-write branch from fc32b76 to 6101a9c Compare October 14, 2026 22:45
@nibzard
nibzard merged commit af88817 into nibzard:main Oct 14, 2026
1 of 3 checks passed
@nibzard

nibzard commented Oct 14, 2026

Copy link
Copy Markdown
Owner

Merged, with two small fixes on top: regenerated the catalog data (the PR was missing the apps/web/public/ sync) and corrected the related: slug for the approval-framework pattern. Content unchanged otherwise — the references all checked out.

🤖 Generated with Claude Code

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.

2 participants