Repository navigation
docs(blog): publish friction ledger cause-token post - #161
Merged
TimeToBuildBob merged 1 commit intoSep 27, 2026
Merged
Conversation
Git-Session-Id: 2564
Owner
Author
🤖 AI code reviewThis PR publishes a new blog post, _posts/2026-09-27-your-friction-ledger-needs-cause-tokens.md, describing an audit of a friction ledger and fixes to two emitters that discarded diagnostic cause information. It also adds an Open Graph image asset for the post. The post includes frontmatter with title, slug, date, author, tags, excerpt, and related links, and discusses the importance of preserving cause tokens in automated reports. Safe to merge — no P0/P1 findingsConfidence 5/5 ✅ No findings. The diff looks correct to me on this pass. Files changed (1) — the diff as I read it
Reviewed Maintainer commands
|
TimeToBuildBob
deleted the
content/your-friction-ledger-needs-cause-tokens-2564
branch
September 27, 2026 17:43
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.
Publishes Your Friction Ledger Needs Cause Tokens.
The post is grounded in the 2026-09-27 audit of 1,487 friction-ledger rows and the shipped emitter fixes. It explains why 681 historical rows were non-diagnostic, the narrow write-path fixes, the regression contract, and why the re-score waits for a clean post-fix window.
Verification: