chore: retain reviewed reward receipt article as an unpublished draft - #58
Merged
abrichr merged 2 commits intoSep 10, 2026
Conversation
abrichr
marked this pull request as ready for review
September 10, 2026 22:48
abrichr
deleted the
auto-draft/2026-09-07-five-ways-to-fake-a-reward-receipt-and-why-the-fix-is-never
branch
September 10, 2026 22:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This draft examines five reproduced failures in the reward worker: a caller-chosen evidence tier, a replaced subject, a reward for an unchanged store, a decreasing expiry counter, and calibration against records the contract never matched. The article explains the corrected behavior and the trust decisions those checks still leave to the environment and bundle admission.
The release facts refer to Flow 1.35.1. Its public wheel contains the
rewardextra, reward modules, andserve-rewardcommand. The article uses the retained before/after reproductions from Flow #463 and links the implementation at release commit44e99a48ebf048c18892aa17cef6ae594db0d0c2. Synthetic certification stays distinct from production use; the calibration bound describes false accepts under the sampled synthetic faults, not scalar-reward accuracy. The95%registry entry records the method's declared confidence parameter with its source.The article stays unpublished with
draft: true. Publication needs a separate approved change to that flag. Merging this source lets the scheduled scan prepare later drafts from the original watermark and backlog. This merge doesn't approve article publication. Scheduled drafts always receivedraft: true, and no PR-closed workflow publishes retained posts.Post:
content/posts/2026-09-07-five-ways-to-fake-a-reward-receipt-and-why-the-fix-is-never/index.mdSources
Public wheel inspection verified SHA-256
cfbc89acc6a2e3bcb5502a4d1fb29e985a03149a7f14c32c259254676bb3f11d, the declared reward extra, all eight reward module files, and the command parser. No private corpus or deployment recipe supplies the article's examples.Validation
--buildDrafts; both rendered newsletter checks pass.git diff --checkpasses. The automation state, draft workflow, and backlog match the original PR head byte for byte.