docs: readme#836
Merged
Merged
Conversation
…ed interaction records
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.
Summary
Top-fold clarity improvement plus a final README polish. The headline uses "signed action records" (the developer-clear hook); the next paragraph defines the formal artifact as "portable signed interaction records" (the protocol-grade term covering decisions, observations, denials, payment events, provisioning events, gateway reports, and bundles). Present-tense framing; the canonical line "Record locally. Verify across boundaries." is unchanged.
Scope (README.md only)
codeandmessage(there is noreasonfield); the example no longer throws dead fallback text.Validation
git diff --checkclean; tooling suite 955 passed (37 files); public-artifact and planning-leak scanners pass.