Add Eusocial Interbeing naming surface

settings/eusocial-interbeing/README.md

@@ -0,0 +1,60 @@
+# Eusocial Interbeing Naming Surface
+
+This setting surface connects Weksa to the Eusocial Interbeing vault at
+`E:\Projects\Eusocial Interbeing`. Its purpose is eventual naming support for
+objects, species, places, institutions, ecological contracts, and technologies in
+languages spoken by the setting's inhabitants.
+
+Weksa should not mint durable names by translating English labels. It should
+derive names from structured meaning, speaker ontology, phonology, morphology,
+register, and history.
+
+## Authority
+
+- Eusocial Interbeing owns setting canon: biology, ecology, cultures, politics,
+  places, species, and use contexts.
+- Weksa owns the language-project pipeline: ontology projection, grammar,
+  morphology, phonology, diachrony, rendering, glossing, and critique.
+- A future language project owns one inhabitant language. Airawa imperial
+  register, pre-imperial Airawa registers, Sa'auei'a family-unit speech, ritual
+  breeding-ground registers, and ecological-partner contact systems should not
+  collapse into one universal naming soup.
+
+## Naming Rule
+
+Names should come after meaning decomposition.
+
+For each candidate object, first define:
+
+- what scale is speaking or naming;
+- whether the name is an endonym, exonym, ritual avoidance term, technical term,
+  imperial administrative term, route-name, child-name, or trade gloss;
+- what the speaker's ontology makes obligatory: memory relation, network status,
+  reciprocity debt, reproductive role, eclipse timing, danger, consent,
+  ownership, or taboo;
+- whether the name is stable, seasonal, situational, inherited, or deliberately
+  evasive.
+
+Only then should Weksa generate surface forms.
+
+## First Language-Project Pressure
+
+Eusocial Interbeing will need languages that can name a world where mutable
+memory exchange is cellular and ecological before it is cultural. A language may
+need obligatory distinctions that English hides:
+
+- connected, disconnected, coerced, infected, or sovereign memory;
+- organism-self, tissue-self, colony-self, family-self, route-self, and
+  landscape-self;
+- seen-under-Umbros, eclipse-timed, light-returning, and anti-Umbros;
+- reciprocal partner, debtor, parasite, host, archive, carrier, and sanctioner;
+- safe-to-name, indirect-name-required, and silence-required.
+
+These are setting pressures, not Weksa engine doctrine.
+
+## Initial Cross-Repo Contract
+
+Until a real language-project state format exists, accepted naming work should
+be recorded as explicit design notes here and referenced from the Eusocial vault.
+Scratch names may appear in working notes, but they are not canon until a
+language project can explain the ontology and form.