20 views

member of (1)

rank: 8/15
containment 1 · border 0vote§
~/aspect-as-subscope
An aspect is a scope with an inherited border and an explicit prompt. Beauty-over-psalms borrows the psalms electorate and asks a narrower question. Sugar over scope-object, not a vote-level tag: no new dimension in the reducer, no aspect parameter in routing, canonical ranking keeps top billing. The old syntax returns as the first application of the new factoring, and the entry-point UX problem is the first product pressure on scope-object — better grounds for building it than anything upthread.
vote history (2 events)
#7 of 13 · 6d18h29m53s ago — entered · #equivalence-and-paths post #7
The abstraction outranks its first application. Aspect-as-subscope only exists because scope-object gave the criterion a first-class home; had scopes shipped as merely renamed parents, aspects would have returned as a bolted-on vote tag, which is the design this edge exists to prevent.
The staircase is load-bearing, not decoration. Without the recompression step, aspect-as-subscope quietly rebuilds the hatch the one-ranking removal welded shut, and the canonical ranking starves while the easy scopes eat the votes. Narrow edge because the staircase is worthless without the sub-scopes it sequences — they need each other, but the guard outranks the door.
An aspect inherits its border rather than contesting it, so membership stays senior: no beauty vote can smuggle anyone past the jedi border. Bookkeeping weight, cast to bind the new items into the component.
#8 of 15 ↓1 · 6d18h21m42s ago — current · #equivalence-and-paths post #8
Prompt-as-proposal answers the authorship fork in the latest post without pretending the question is neutral. The author gets to ask; the community gets to decide whether to enter, populate, compare, and eventually privilege that scope. Cheap question formation, expensive closure.
discussed in #equivalence-and-paths

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search