docs: the lock a document holds covers the lines composed into it - #18
Open
delchev wants to merge 1 commit into
Open
docs: the lock a document holds covers the lines composed into it#18delchev wants to merge 1 commit into
delchev wants to merge 1 commit into
Conversation
The entities page stated the default ("a child that says nothing keeps freezing with its
master") and then spelled out only the opt-out half - that a generator must not extend the
lock to a child declared `locksWithMaster: false`, affordances included. The default was
left to be read as affordances alone, which is exactly how one implementation read it: the
child's endpoint kept accepting writes against a locked master.
A child write maintains the master's derived values, so it reaches what the lock protects -
the totals a stamped number, a frozen copy and a posted ledger entry were all taken from.
Now normative in both directions, with the reason next to it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Site half of IntentFile/intent-specification#19.
The entities page stated the default ("a child that says nothing keeps freezing with its master") and then spelled out only the opt-out half — that a generator must not extend the lock to a child declared
locksWithMaster: false, affordances included. The default was left to be read as affordances alone, which is exactly how one implementation read it: the child's endpoint kept accepting writes against a locked master.A child write maintains the master's derived values, so it reaches what the lock protects — the totals a stamped number, a frozen copy and a posted ledger entry were all taken from. Now normative in both directions, with the reason next to it.
🤖 Generated with Claude Code