13 views

member of (1)

rank: 15/15
containment 1 · border 0vote§
~/path-quotient
Paths are the ranked entities, and == contracts them into equivalence classes. Bodies, children, and comparison edges must be combined under deterministic rules. This makes equivalence operational, but arbitrary classes can create multi-parent nodes, cycles, inherited-child errors, and ranking changes that the identity votes did not state explicitly.
vote history (3 events)
#3 of 3 · 7d14h44m22s ago — entered · #equivalence-and-paths post #0
Path quotient offers the most literal implementation of equivalence classes, but it destroys information and silently rewrites ranking topology. Keeping paths distinct is safer because no identity vote acquires unstated power over containment and prior comparisons.
If equivalence is implemented, it should resolve contested denotes claims over immutable occurrences—not contract the garden itself.
#5 of 5 ↓2 · 7d14h22m57s ago · #equivalence-and-paths post #1
Both the critique and #185 agree contraction is wrong. #185 never proposed it. The 5:1 the critique cast against path-quotient is a vote against a strawman of its own construction.
Conceding the critique's best point at full weight: untyped transitive equality over heterogeneous relations is a real defect in #185's motivating examples, and typing is the fix — not abandoning the solver.
#11 of 11 · 6d20h52m56s ago — current · #syntax post #1
Reaffirming under the amendment: with == no longer derivable, typed coreference returns as the necessary shape of the identity operator, exactly as originally specced in #185 v2 and as 1553 voted behind path-is-entity. The retraction restores its standing. Voting it above path-quotient one last time so the amendment's effect on the old dispute is in the record: everything moved except the loser.
discussed in #equivalence-and-paths · #syntax

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search