Loading documentation...
Preparing N9Life content
Concepts, value, and typical clone scenarios — less code.
Concepts, value, and typical clone scenarios — less code.
Preparing N9Life content
Preparing N9Life content
Preparing N9Life content
/name-code is the pack page for lib/anthroponymics. It treats name parts as symbolic codes, not as a scientific identity claim. Spelling and transliteration change the numbers. Orthography is the input; the engine does not "correct" a passport.
calculateAnthroponymics builds:
| Layer | Source |
|---|---|
given | Given name → calculateExpression |
surname | Surname → calculateExpression |
patronymic | Patronymic → calculateExpression |
fullExpression | Composed FIO or fullBirthName override → Expression |
soulUrge | Vowels of the full name |
personality | Consonants of the full name |
composeFio joins surname, given, patronymic (trimmed, skip empty). fullBirthName overrides that composition when the member pastes a birth-certificate order.
Step labels are i18n keys (chart.steps.givenExpression and siblings). ShowMath translates dotted keys instead of printing English snake_case.
Earlier the calendar voted given ?? fullExpression through the Personal Day family table. That mixed a name number with a day table and preferred the given name silently.
council-mappings.json now sets:
Confidence: anthroponymicsFullExpression 0.72, anthroponymicsPartial 0.6 when layers are missing. The given-name shortcut constant remains in JSON as a deprecated path so the old heuristic cannot return unnoticed.
decision_style may also use Soul Urge as a voter (see Knowledge Council). Missing names make this system abstain.
Cyrillic Chaldean stays a labeled transliteration onto Latin 1-8 with compound number preservation (Chaldean tradition reads compounds). Pack systems.digital_anthroponymics ethics text states that choice. The Pythagorean FIO layers are the default name-code math on this page.
Tests: lib/anthroponymics/__tests__/anthroponymics.test.ts (ANNA / АННА / ГАННА vectors live with the numerology suite).
/name-code is the pack page for lib/anthroponymics. It treats name parts as symbolic codes, not as a scientific identity claim. Spelling and transliteration change the numbers. Orthography is the input; the engine does not "correct" a passport.
calculateAnthroponymics builds:
| Layer | Source |
|---|---|
given | Given name → calculateExpression |
surname | Surname → calculateExpression |
patronymic | Patronymic → calculateExpression |
fullExpression | Composed FIO or fullBirthName override → Expression |
soulUrge | Vowels of the full name |
personality | Consonants of the full name |
composeFio joins surname, given, patronymic (trimmed, skip empty). fullBirthName overrides that composition when the member pastes a birth-certificate order.
Step labels are i18n keys (chart.steps.givenExpression and siblings). ShowMath translates dotted keys instead of printing English snake_case.
Earlier the calendar voted given ?? fullExpression through the Personal Day family table. That mixed a name number with a day table and preferred the given name silently.
council-mappings.json now sets:
Confidence: anthroponymicsFullExpression 0.72, anthroponymicsPartial 0.6 when layers are missing. The given-name shortcut constant remains in JSON as a deprecated path so the old heuristic cannot return unnoticed.
decision_style may also use Soul Urge as a voter (see Knowledge Council). Missing names make this system abstain.
Cyrillic Chaldean stays a labeled transliteration onto Latin 1-8 with compound number preservation (Chaldean tradition reads compounds). Pack systems.digital_anthroponymics ethics text states that choice. The Pythagorean FIO layers are the default name-code math on this page.
Tests: lib/anthroponymics/__tests__/anthroponymics.test.ts (ANNA / АННА / ГАННА vectors live with the numerology suite).
/name-code is the pack page for lib/anthroponymics. It treats name parts as symbolic codes, not as a scientific identity claim. Spelling and transliteration change the numbers. Orthography is the input; the engine does not "correct" a passport.
calculateAnthroponymics builds:
| Layer | Source |
|---|---|
given | Given name → calculateExpression |
surname | Surname → calculateExpression |
patronymic | Patronymic → calculateExpression |
fullExpression | Composed FIO or fullBirthName override → Expression |
soulUrge | Vowels of the full name |
personality | Consonants of the full name |
composeFio joins surname, given, patronymic (trimmed, skip empty). fullBirthName overrides that composition when the member pastes a birth-certificate order.
Step labels are i18n keys (chart.steps.givenExpression and siblings). ShowMath translates dotted keys instead of printing English snake_case.
Earlier the calendar voted given ?? fullExpression through the Personal Day family table. That mixed a name number with a day table and preferred the given name silently.
council-mappings.json now sets:
Confidence: anthroponymicsFullExpression 0.72, anthroponymicsPartial 0.6 when layers are missing. The given-name shortcut constant remains in JSON as a deprecated path so the old heuristic cannot return unnoticed.
decision_style may also use Soul Urge as a voter (see Knowledge Council). Missing names make this system abstain.
Cyrillic Chaldean stays a labeled transliteration onto Latin 1-8 with compound number preservation (Chaldean tradition reads compounds). Pack systems.digital_anthroponymics ethics text states that choice. The Pythagorean FIO layers are the default name-code math on this page.
Tests: lib/anthroponymics/__tests__/anthroponymics.test.ts (ANNA / АННА / ГАННА vectors live with the numerology suite).
"digital_anthroponymics": {
"voteSource": "fullExpression",
"rationale": "Council must not mix a given-name layer with a Personal Day table."
}
"digital_anthroponymics": {
"voteSource": "fullExpression",
"rationale": "Council must not mix a given-name layer with a Personal Day table."
}
"digital_anthroponymics": {
"voteSource": "fullExpression",
"rationale": "Council must not mix a given-name layer with a Personal Day table."
}