Repository navigation
[autopilot] skills: keep volatile facts and measurement protocols out of claim ledgers - #156
Merged
Merged
Conversation
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.
Extends the claim-ledger section of cross-surface-changes with two rules. (1) Facts that change on their own (ratings, latest version, listing order) belong in a dated, non-citable observations section, not as stable ledger identifiers. (2) Measured figures carry their evaluation protocol everywhere they are quoted, so two surfaces never present the same metric under different protocols. Motivated by repeated copy drift where a quoted volatile fact or protocol-less number later read as a regression or went stale. No registration changes (existing skill).