Also, I absolutely love the word “shard” but my brain refuses to use it because then it feels like we won’t get credit for discovering these notions by ourselves. Well, also just because the words “domain”, “context”, “scope”, “niche”, “trigger”, “preimage” (wrt to a neural function/policy / “neureme”) adequately serve the same purpose and are currently more semantically/semiotically granular in my head.
EDIT: ig I use “scope” and “domain” in a way which doesn’t neatly mean one is a subset of the other. I want to be able to distinguish between “the set of inputs it’s currently applied to” and “the set of inputs it should be applied to” and “the set of inputs it could be applied to”, but I don’t have adequate words here.
This is a good question, especially since there’ve been some short form posts recently that are high quality and would’ve made good top-level posts—after all, posts can be short.
Epic Lizka post is epic.
Also, I absolutely love the word “shard” but my brain refuses to use it because then it feels like we won’t get credit for discovering these notions by ourselves. Well, also just because the words “domain”, “context”, “scope”, “niche”, “trigger”, “preimage” (wrt to a neural function/policy / “neureme”) adequately serve the same purpose and are currently more semantically/semiotically granular in my head.
trigger/preimage ⊆ scope⊆ domain[1]“niche” is a category in function space (including domain, operation, and codomain), “domain” is a set.
“scope” is great because of programming connotations and can be used as a verb. “This neural function is scoped to these contexts.”
EDIT: ig I use “scope” and “domain” in a way which doesn’t neatly mean one is a subset of the other. I want to be able to distinguish between “the set of inputs it’s currently applied to” and “the set of inputs it should be applied to” and “the set of inputs it could be applied to”, but I don’t have adequate words here.