Repository navigation
feat(WO72): gates require an anchor (protocol + convention or no gate) - #322
Merged
Merged
Conversation
GateSpec.anchor (required, non-empty) joins convention: a number without its aggregation convention AND its protocol anchor is not a gate. Recipes carry real anchors (run-047/run-059/run-066; fas -> the WO47 ledger section, docs split, corpus-level). Finding recorded, not silently changed: the fas gate threshold (corpus-level 0.0052) predates the WO47 closure finding (RC line = 0.603 row-mean, run-077); the threshold itself is an owner decision.
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.
Implements WO72: GateSpec.anchor is required (non-empty string naming the protocol/ledger section a gate line is anchored to), joining the existing required convention (row-mean vs corpus-level -- the fas scar law).