docs: state must be idempotent commutative monoid, not just commutative - #112
Open
sanity wants to merge 1 commit into
Open
docs: state must be idempotent commutative monoid, not just commutative#112sanity wants to merge 1 commit into
sanity wants to merge 1 commit into
Conversation
The manual pages, FAQ, and slides described contract state merge as only requiring commutativity, but the whitepaper and stdlib trait docs require associativity and idempotence too (state forms an idempotent commutative monoid / join-semilattice). Align wording across the site. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018gMSXHaQ2rXKGfAVWKqk11
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.
Problem
Manual pages, FAQ, and a slide deck described contract state merge as only requiring commutativity. The actual requirement (per freenet-stdlib's ContractInterface docs and the whitepaper) is that merge is associative, commutative, AND idempotent (an idempotent commutative monoid / join-semilattice).
Approach
Align wording across the site with the whitepaper's terminology.
Testing
Doc-only change (markdown + slide HTML content, no code).
[AI-assisted - Claude]