Repository navigation
Read a node's written rank as its rank - #147
Merged
Merged
Conversation
Roadmap G8, without the migration: a tree node that writes `rank`, a word or `null`, sits at that rank wherever a node's rank matters, and a node that writes none keeps its record's. `Tree.rank` is the one reading; the placement claim's `rank` carries it (`rankAsPrinted` still marks a written one, now on a root's usage for a word as well as a null), the genus-group order check checks a printed word by that word, the open-nomenclature checks and the node checks read the open form at its node's rank, and the derived coverage counts each node at it. The store's `node_rank` reads the claim back for the listings, the ancestors chains, the content rows and the history's ranks, so Gill & Caster 1960 print "Subclass Homostelea" and Whiteaves 1897 his orders, and `history crinoidea` counts each paper at the rank it printed. The protologue check is unchanged. Regenerated claims: 115 placements take their printed rank and 114 root usages gain `rankAsPrinted`; the manifest, names and repositories are unchanged. Co-Authored-By: Claude Fable 5.1 <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.
Roadmap G8, without the migration: a tree node that writes
rank, a word ornull, sits at that rank wherever a node's rank matters, and a node that writes none keeps its record's.Tree.rankis the one reading; the placement claim'srankcarries it (rankAsPrintedstill marks a written one, now on a root's usage for a word as well as a null), the genus-group order check checks a printed word by that word, the open-nomenclature checks and the node checks read the open form at its node's rank, and the derived coverage counts each node at it. The store'snode_rankreads the claim back for the listings, the ancestors chains, the content rows and the history's ranks, so Gill & Caster 1960 print "Subclass Homostelea" and Whiteaves 1897 his orders, andhistory crinoideacounts each paper at the rank it printed. The protologue check is unchanged.Regenerated claims: 115 placements take their printed rank and 114 root usages gain
rankAsPrinted; the manifest, names and repositories are unchanged.