Hugwis mental models - Revision history

SN2rname: /* "Processing" */replace 'departure' with 'localization' in example

2025-02-07T12:27:50Z

"Processing": replace 'departure' with 'localization' in example

← Older revision		Revision as of 12:27, 7 February 2025
Line 57:		Line 57:

	=== Concept-emotion distance ===		=== Concept-emotion distance ===
	Words that are closely linked to certain emotions, like "death", "fight" and "~~departure~~", are processed differently. It's hard to determine how exactly so, though these words have a different "feel" to neutral nouns. I believe they are encoded to be both more intuitive and more precise, as opposed to intuitive but fuzzy words like "happy" and "sad", or precise but abstract words like "ontology" or "cyclohexane".		Words that are closely linked to certain emotions, like "death", "fight" and "localization", are processed differently. It's hard to determine how exactly so, though these words have a different "feel" to neutral nouns. I believe they are encoded to be both more intuitive and more precise, as opposed to intuitive but fuzzy words like "happy" and "sad", or precise but abstract words like "ontology" or "cyclohexane".

	=== Dichotomies ===		=== Dichotomies ===

SN2rname at 12:20, 7 February 2025

2025-02-07T12:20:10Z

← Older revision		Revision as of 12:20, 7 February 2025
Line 1:		Line 1:
	:''This article won't be updated very frequently, but I'm working on it and intend to come back to it later. Hence, it is my wish that this article be kept. Thank you''		:''This article won't be updated very frequently, but I'm working on it and intend to come back to it later. Hence, it is my wish that this article be kept. Thank you. (2025)''

	The '''Hugwis mental models''' (HOOG-wiss) is the underlying conceptual structure uniting all conlangs made by [[User:SN2rname\|SN2]]. ''Hugwis'' is an acronym of all the conlangs I have planned~~, none of which is complete yet~~.		The '''Hugwis mental models''' (HOOG-wiss) is the underlying conceptual structure uniting all conlangs made by [[User:SN2rname\|SN2]]. ''Hugwis'' is an acronym of all the conlangs I have planned.

	== Background ==		== Background ==
Line 48:		Line 48:
	It's true is_reflexive seems redundant here, because a reflexive action can be represented by setting the agent and patient to the same, but this additional property may be an artifact introduced by language, namely the reflexive prefix like "self-".		It's true is_reflexive seems redundant here, because a reflexive action can be represented by setting the agent and patient to the same, but this additional property may be an artifact introduced by language, namely the reflexive prefix like "self-".

			== "Processing" ==
	=== Visual processing (not mapped) ===		=== Visual processing (not mapped) ===
	Edge-detect and intersection-detect.		Edge-detect and intersection-detect.
Line 53:		Line 54:
	When viewing a flow chart, the nodes (intersections) are most important. With a map, I see intersections rather than roads and alleys. This is useful in many ways, because interesting places are often found at intersections, and I could better memorize roads which do not allow pedestrians to cross. Sometimes this impedes learning, as focusing on nodes can make me lose sight of shapes.		When viewing a flow chart, the nodes (intersections) are most important. With a map, I see intersections rather than roads and alleys. This is useful in many ways, because interesting places are often found at intersections, and I could better memorize roads which do not allow pedestrians to cross. Sometimes this impedes learning, as focusing on nodes can make me lose sight of shapes.

	After using Bézier curves for animation and font-making, some curved shapes ~~are even represented~~ as quadratic Bézier splines.		After using Bézier curves for animation and font-making, I even started to see some curved shapes as quadratic Bézier splines, though I can't yet work out waypoints for a random squiggle by a glance yet.

	~~== "Processing" ==~~
	=== Concept-emotion distance ===		=== Concept-emotion distance ===
	Words that are closely linked to certain emotions, like "death", "fight" and "departure", are processed differently. It's hard to determine how exactly, ~~although~~ these words have a different "feel" to neutral nouns. I believe they are more intuitive ~~but also~~ more precise, as opposed to "fuzzy~~" worsd~~ like "happy" and "sad".		Words that are closely linked to certain emotions, like "death", "fight" and "departure", are processed differently. It's hard to determine how exactly so, though these words have a different "feel" to neutral nouns. I believe they are encoded to be both more intuitive and more precise, as opposed to intuitive but fuzzy words like "happy" and "sad", or precise but abstract words like "ontology" or "cyclohexane".

	=== Dichotomies ===		=== Dichotomies ===
	All of my conlangs can be said to have two word classes. Even if I know many attributes of things exist on a sliding scale, I still see black and white, artificial and natural, dense and light, hard and soft, and other opposition pairs. In Hwnic, this system is modernized to contain a "somewhere in between" and a "does not apply".		All of my conlangs can be said to have two word classes. Even if I know many attributes of things exist on a sliding scale, I still see black and white, artificial and natural, dense and light, hard and soft, and other opposition pairs.

			In Hwnic, this system is modernized to contain a "somewhere in between" and a "does not apply".

	== Design choices of Hwnic ==		== Design choices of Hwnic ==
	[[Hwnic]] is named after the "window handle" type HWND in WinAPI. (It is not related to HWN Energy acquisitions, printer models, or the surname Hwang.) It is thought to have a precise structure like a programming language, as it arose out of a desire to limit the chaos/ambiguity aspect of my thinking. However, this is not upheld at all times now.		[[Hwnic]] is named after the "window handle" type HWND in WinAPI. (It is not related to HWN Energy acquisitions, printer models, or the surname Hwang.) It is thought to have a precise structure like a programming language, as it arose out of a desire to limit the chaos/ambiguity aspect of my thinking. However, this is not upheld at all times now.
			<!--
	* agglutinative, but limiting the stacking of affixes		* agglutinative, but limiting the stacking of affixes
	* Capital sigma sum, e.g. value 1, value 2, ..., value n. duplicative, sequential, or recursive		* Capital sigma sum, e.g. value 1, value 2, ..., value n. duplicative, sequential, or recursive
Line 71:		Line 73:
	* reduplication, doubling letter to show morpheme boundary, from ubosvi, mernc, rnsoc /z/		* reduplication, doubling letter to show morpheme boundary, from ubosvi, mernc, rnsoc /z/
	* mxa - mxu: see - sleep		* mxa - mxu: see - sleep
			-->

SN2rname: /* "Processing" */

2025-02-07T12:09:54Z

"Processing"

← Older revision		Revision as of 12:09, 7 February 2025
Line 54:		Line 54:

	After using Bézier curves for animation and font-making, some curved shapes are even represented as quadratic Bézier splines.		After using Bézier curves for animation and font-making, some curved shapes are even represented as quadratic Bézier splines.

			== "Processing" ==
			=== Concept-emotion distance ===
			Words that are closely linked to certain emotions, like "death", "fight" and "departure", are processed differently. It's hard to determine how exactly, although these words have a different "feel" to neutral nouns. I believe they are more intuitive but also more precise, as opposed to "fuzzy" worsd like "happy" and "sad".

			=== Dichotomies ===
			All of my conlangs can be said to have two word classes. Even if I know many attributes of things exist on a sliding scale, I still see black and white, artificial and natural, dense and light, hard and soft, and other opposition pairs. In Hwnic, this system is modernized to contain a "somewhere in between" and a "does not apply".

	== Design choices of Hwnic ==		== Design choices of Hwnic ==

	[[Hwnic]] is named after the "window handle" type HWND in WinAPI. (It is not related to HWN Energy acquisitions, printer models, or the surname Hwang.) It is thought to have a precise structure like a programming language, as it arose out of a desire to limit the chaos/ambiguity aspect of my thinking. However, this is not upheld at all times now.		[[Hwnic]] is named after the "window handle" type HWND in WinAPI. (It is not related to HWN Energy acquisitions, printer models, or the surname Hwang.) It is thought to have a precise structure like a programming language, as it arose out of a desire to limit the chaos/ambiguity aspect of my thinking. However, this is not upheld at all times now.

SN2rname: /* Background */

2025-01-31T22:46:10Z

Background

← Older revision		Revision as of 22:46, 31 January 2025
Line 3:		Line 3:
	The '''Hugwis mental models''' (HOOG-wiss) is the underlying conceptual structure uniting all conlangs made by [[User:SN2rname\|SN2]]. ''Hugwis'' is an acronym of all the conlangs I have planned, none of which is complete yet.		The '''Hugwis mental models''' (HOOG-wiss) is the underlying conceptual structure uniting all conlangs made by [[User:SN2rname\|SN2]]. ''Hugwis'' is an acronym of all the conlangs I have planned, none of which is complete yet.

	== ~~Theory and background~~ ==		== Background ==
	The underlying assumptions behind Hugwis are (a) an ''a priori'' conlang that is made from scratch reflects how the creator organizes and categorizes concepts mentally, (b) I can gain understanding of my own mental model by using itself to study itself, and (c) this mental model is relatively stable over time.		The underlying assumptions behind Hugwis are (a) an ''a priori'' conlang that is made from scratch reflects how the creator organizes and categorizes concepts mentally, (b) I can gain understanding of my own mental model by using itself to study itself, and (c) this mental model is relatively stable over time.

Line 12:		Line 12:
	The principles of Hugwis are redundancy, abstraction, systemization, chaos/ambiguity, preservation of detail, and flexibility/extensibility.		The principles of Hugwis are redundancy, abstraction, systemization, chaos/ambiguity, preservation of detail, and flexibility/extensibility.

			== "Structs" ==
	=== Basic structure ===		=== Basic structure ===
	The basic unit of Hugwis is the ''concept''. Information stored in the brain is thought to be encoded in a highly interconnected, mostly directional graph of concepts, and each concept is a node that links to other nodes.		The basic unit of Hugwis is the ''concept''. Information stored in the brain is thought to be encoded in a highly interconnected, mostly directional graph of concepts, and each concept is a node that links to other nodes.
Line 41:		Line 42:
	=== Action ===		=== Action ===
	agent, action, patient, properties[], ..., is_reflexive, is_agent_unknown, is_patient_unknown		agent, action, patient, properties[], ..., is_reflexive, is_agent_unknown, is_patient_unknown

			Isn't "is ... unknown" an anti-pattern? In programming this may be true, but as a rule, boolean values in Hugwis default to false, and the attributes get a negation in the names.

	The passive voice in Hugwis is simply an action with is_agent_unknown = true, so my conlangs often lack a separate passive voice.		The passive voice in Hugwis is simply an action with is_agent_unknown = true, so my conlangs often lack a separate passive voice.
	It's true is_reflexive seems redundant here, because a reflexive ~~axction~~ can be represented by setting the agent and patient to the same, but this additional property may be an artifact introduced by language, namely the reflexive prefix like "self-".		It's true is_reflexive seems redundant here, because a reflexive action can be represented by setting the agent and patient to the same, but this additional property may be an artifact introduced by language, namely the reflexive prefix like "self-".

	=== Visual processing ===		=== Visual processing (not mapped) ===
	Edge-detect and intersection-detect.		Edge-detect and intersection-detect.

	When viewing a flow chart, the nodes (intersections) are most important. With a map, I see intersections rather than roads and alleys. This is useful in many ways, because interesting places are often found at intersections, and I could better memorize roads which do not allow pedestrians to cross. Sometimes this impedes learning, as focusing on nodes can make me lose sight of shapes.		When viewing a flow chart, the nodes (intersections) are most important. With a map, I see intersections rather than roads and alleys. This is useful in many ways, because interesting places are often found at intersections, and I could better memorize roads which do not allow pedestrians to cross. Sometimes this impedes learning, as focusing on nodes can make me lose sight of shapes.

	After ~~Bezier~~ curves for animation and font-making, some curved shapes are even represented as quadratic ~~Bezier~~ splines.		After using Bézier curves for animation and font-making, some curved shapes are even represented as quadratic Bézier splines.

	== Design choices of Hwnic ==		== Design choices of Hwnic ==

SN2rname: /* Theory and background */

2025-01-31T22:40:22Z

Theory and background

← Older revision		Revision as of 22:40, 31 January 2025
Line 34:		Line 34:

	In Hugwis, the most prominent feature of a word is its length: 1-2 very short; 3-4 short; 5-8 medium; 9-16 long; 17+ very long (inclusive). This is because when I try to recall an unfamiliar word, the first information I retrieve is often this estimate of its length.		In Hugwis, the most prominent feature of a word is its length: 1-2 very short; 3-4 short; 5-8 medium; 9-16 long; 17+ very long (inclusive). This is because when I try to recall an unfamiliar word, the first information I retrieve is often this estimate of its length.

			Consistent with existing research, my brain may assign extra importance for the first and last elements in a list. I sometimes misspell words by switching two letters in the middle (metathesis), like "hazadrous" and "revelant", and at one time I often forgot trisyllabic laxing, like "maintainance" and "exclaimation", although I seldom misremember the start and end, even with silent letters like "ptosis" and "choux". In Hwnic, the existence of circumfixes is based on this focus on start and end.

	As a rule, when thinking about a word, I typically do not attempt to split the entire word into individual morphemes: "uninformed" is "un-" + "informed", and "interest" is even encoded as a single component.		As a rule, when thinking about a word, I typically do not attempt to split the entire word into individual morphemes: "uninformed" is "un-" + "informed", and "interest" is even encoded as a single component.
Line 42:		Line 44:
	The passive voice in Hugwis is simply an action with is_agent_unknown = true, so my conlangs often lack a separate passive voice.		The passive voice in Hugwis is simply an action with is_agent_unknown = true, so my conlangs often lack a separate passive voice.
	It's true is_reflexive seems redundant here, because a reflexive axction can be represented by setting the agent and patient to the same, but this additional property may be an artifact introduced by language, namely the reflexive prefix like "self-".		It's true is_reflexive seems redundant here, because a reflexive axction can be represented by setting the agent and patient to the same, but this additional property may be an artifact introduced by language, namely the reflexive prefix like "self-".

			=== Visual processing ===
			Edge-detect and intersection-detect.

			When viewing a flow chart, the nodes (intersections) are most important. With a map, I see intersections rather than roads and alleys. This is useful in many ways, because interesting places are often found at intersections, and I could better memorize roads which do not allow pedestrians to cross. Sometimes this impedes learning, as focusing on nodes can make me lose sight of shapes.

			After Bezier curves for animation and font-making, some curved shapes are even represented as quadratic Bezier splines.

	== Design choices of Hwnic ==		== Design choices of Hwnic ==

SN2rname: note

2025-01-31T22:35:46Z

note

← Older revision		Revision as of 22:35, 31 January 2025
Line 1:		Line 1:
			:''This article won't be updated very frequently, but I'm working on it and intend to come back to it later. Hence, it is my wish that this article be kept. Thank you''

	The '''Hugwis mental models''' (HOOG-wiss) is the underlying conceptual structure uniting all conlangs made by [[User:SN2rname\|SN2]]. ''Hugwis'' is an acronym of all the conlangs I have planned, none of which is complete yet.		The '''Hugwis mental models''' (HOOG-wiss) is the underlying conceptual structure uniting all conlangs made by [[User:SN2rname\|SN2]]. ''Hugwis'' is an acronym of all the conlangs I have planned, none of which is complete yet.

SN2rname: /* Theory and background */

2025-01-26T09:59:37Z

Theory and background

← Older revision		Revision as of 09:59, 26 January 2025
Line 27:		Line 27:

	The two forms of certain numerals is linked to the non-symbolic/symbolic distinction. The number 20 is usually considered symbolic, since I can't glance at an unordered collection of 20 objects and derive the numeral immediately, but then an ordered array of 4-by-5 objects is non-symbolic. The first form is ''xoqukul'' "two_digits-two-zero", and the second form is ''cestogis'' "four-times-five".		The two forms of certain numerals is linked to the non-symbolic/symbolic distinction. The number 20 is usually considered symbolic, since I can't glance at an unordered collection of 20 objects and derive the numeral immediately, but then an ordered array of 4-by-5 objects is non-symbolic. The first form is ''xoqukul'' "two_digits-two-zero", and the second form is ''cestogis'' "four-times-five".

			=== WordAlphabet ===
			length_estimate, morpheme_first, morpheme_last, components[], language_origin

			In Hugwis, the most prominent feature of a word is its length: 1-2 very short; 3-4 short; 5-8 medium; 9-16 long; 17+ very long (inclusive). This is because when I try to recall an unfamiliar word, the first information I retrieve is often this estimate of its length.

			As a rule, when thinking about a word, I typically do not attempt to split the entire word into individual morphemes: "uninformed" is "un-" + "informed", and "interest" is even encoded as a single component.

			=== Action ===
			agent, action, patient, properties[], ..., is_reflexive, is_agent_unknown, is_patient_unknown

			The passive voice in Hugwis is simply an action with is_agent_unknown = true, so my conlangs often lack a separate passive voice.
			It's true is_reflexive seems redundant here, because a reflexive axction can be represented by setting the agent and patient to the same, but this additional property may be an artifact introduced by language, namely the reflexive prefix like "self-".

	== Design choices of Hwnic ==		== Design choices of Hwnic ==

SN2rname: /* Theory and background */design choices for numerals

2025-01-26T09:51:02Z

Theory and background: design choices for numerals

← Older revision		Revision as of 09:51, 26 January 2025
Line 17:		Line 17:
	* CORE attributes define the concept;		* CORE attributes define the concept;
	* EVAL attributes are evaluated from other attributes of the same concept;		* EVAL attributes are evaluated from other attributes of the same concept;
	* An attribute may have the value of ~~the concept itself~~, or nothing. ~~This~~ nothing is just an ordinary abstract concept that I intuitively understand, and need not be described with words. Here, the nothing ''does'' noth.		* An attribute may have the value of (null), or nothing. The (null) indicates information that has been forgotten. The nothing is in predicates like "nothing can go faster than light", and is just an ordinary abstract concept that I intuitively understand, and need not be described with words. Here, the nothing ''does'' noth.

			In the earliest iteration, a complex concept was described as a C-style struct. (I once fantasized about simulating my mind on my laptop.) Now, it is described with a formal grammar, and I may make a template to present them here with more ease.

			=== Numbers ===
			concept int, OR n_components (int), components[ digits[] ], (outgoing links: cultural meanings, error/status codes, and the like)

			Consistent with existing research, Hugwis has a distinction between non-symbolic numerals, like "two" in "two apples", and symbolic numerals, like π or -3250. In numerical operations, numbers are seen as purely conceptual tokens that can be manipulated based on conventions/rules, which these rules are designed to describe features of the Universe, and are not arbitrary.

			The two forms of certain numerals is linked to the non-symbolic/symbolic distinction. The number 20 is usually considered symbolic, since I can't glance at an unordered collection of 20 objects and derive the numeral immediately, but then an ordered array of 4-by-5 objects is non-symbolic. The first form is ''xoqukul'' "two_digits-two-zero", and the second form is ''cestogis'' "four-times-five".

	== Design choices of Hwnic ==		== Design choices of Hwnic ==

SN2rname: /* Theory and background */

2025-01-26T09:44:42Z

Theory and background

← Older revision		Revision as of 09:44, 26 January 2025
Line 2:		Line 2:

	== Theory and background ==		== Theory and background ==
	The underlying assumptions behind Hugwis are (a) an ''a priori'' conlang that is made from scratch reflects how the creator organizes and categorizes concepts mentally, (b) ~~one~~ can gain understanding of ~~one's~~ own mental model using itself, and (c) this mental model is relatively stable.		The underlying assumptions behind Hugwis are (a) an ''a priori'' conlang that is made from scratch reflects how the creator organizes and categorizes concepts mentally, (b) I can gain understanding of my own mental model by using itself to study itself, and (c) this mental model is relatively stable over time.

	Since I was a kid, the way I speak has often confused people, even when I was trying to be normal. I have often felt a need to make up new words, to describe things better or just for fun. When I was a teenager I started to make up my own syntax too, like *"the flickering property of the lights" for "the lights keep flickering", or "than better one" for "better than the other". In time, I started to realize I organize concepts in a peculiar fashion, and I spent some time seeking the reason why.		Since I was a kid, the way I speak has often confused people, even when I was trying to be normal. I have often felt a need to make up new words, to describe things better or just for fun. When I was a teenager I started to make up my own syntax too, like *"the flickering property of the lights" for "the lights keep flickering", or "than better one" for "better than the other". In time, I started to realize I organize concepts in a peculiar fashion, and I spent some time seeking the reason why.
Line 9:		Line 9:

	The principles of Hugwis are redundancy, abstraction, systemization, chaos/ambiguity, preservation of detail, and flexibility/extensibility.		The principles of Hugwis are redundancy, abstraction, systemization, chaos/ambiguity, preservation of detail, and flexibility/extensibility.

			=== Basic structure ===
			The basic unit of Hugwis is the ''concept''. Information stored in the brain is thought to be encoded in a highly interconnected, mostly directional graph of concepts, and each concept is a node that links to other nodes.
			A concept may be simple, like the built-in concrete nouns, counting numbers, or complex, with its own tree structure.
			There are several types of attributes a complex concept hold:
			* DEFAULT (usually hidden), list of concepts that link to and link from the current one;
			* CORE attributes define the concept;
			* EVAL attributes are evaluated from other attributes of the same concept;
			* An attribute may have the value of the concept itself, or nothing. This nothing is just an ordinary abstract concept that I intuitively understand, and need not be described with words. Here, the nothing ''does'' noth.

	== Design choices of Hwnic ==		== Design choices of Hwnic ==

SN2rname: /* Theory and background */

2025-01-24T11:20:08Z

Theory and background

← Older revision		Revision as of 11:20, 24 January 2025
Line 9:		Line 9:

	The principles of Hugwis are redundancy, abstraction, systemization, chaos/ambiguity, preservation of detail, and flexibility/extensibility.		The principles of Hugwis are redundancy, abstraction, systemization, chaos/ambiguity, preservation of detail, and flexibility/extensibility.

			== Design choices of Hwnic ==

			[[Hwnic]] is named after the "window handle" type HWND in WinAPI. (It is not related to HWN Energy acquisitions, printer models, or the surname Hwang.) It is thought to have a precise structure like a programming language, as it arose out of a desire to limit the chaos/ambiguity aspect of my thinking. However, this is not upheld at all times now.

			* agglutinative, but limiting the stacking of affixes
			* Capital sigma sum, e.g. value 1, value 2, ..., value n. duplicative, sequential, or recursive
			* conjunctions such as ''elo''
			* READ DATA formalism (mapping): If it {sunny, rain, snow} tomorrow, I'll {go to the park, go to the seaside, stay at home}
			* reduplication, doubling letter to show morpheme boundary, from ubosvi, mernc, rnsoc /z/
			* mxa - mxu: see - sleep