From f45529b50950443557090c1699a9a67dce31b7cd Mon Sep 17 00:00:00 2001
From: Meta Vens <rwvens@hotmail.com>
Date: Mon, 18 May 2026 01:03:44 +0100
Subject: [PATCH] Add Eusocial Interbeing naming surface

---
 settings/eusocial-interbeing/README.md | 60 ++++++++++++++++++++++++++
 state/map.yaml                         |  8 ++++
 state/scratch.md                       |  3 ++
 3 files changed, 71 insertions(+)
 create mode 100644 settings/eusocial-interbeing/README.md

diff --git a/settings/eusocial-interbeing/README.md b/settings/eusocial-interbeing/README.md
new file mode 100644
index 0000000..270909b
--- /dev/null
+++ b/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.
diff --git a/state/map.yaml b/state/map.yaml
index 190fe1c..42ca815 100644
--- a/state/map.yaml
+++ b/state/map.yaml
@@ -143,6 +143,10 @@ accepted_design:
   - `docs/best-modern-approach.md` is the current doctrine for conceptual
     ontology, root generation, morphology, syntax, lexical semantics,
     interlingua, diachrony, and model-assisted consistency.
+  - Eusocial Interbeing is a second setting collaboration surface. It needs
+    inhabitant-language names derived from speaker ontology, register,
+    phonology, morphology, diachrony, and setting context rather than direct
+    English label translation.
 
 open_questions:
   - Which implementation language best serves the first usable engine?
@@ -155,6 +159,9 @@ open_questions:
   - How much deterministic validation belongs in v0?
   - What is the minimal Rust to Dust language-project slice that proves the
     engine without hard-coding the setting into it?
+  - What minimal Eusocial Interbeing language-project slice can prove naming for
+    Airawa, Sa'auei'a, ecological partner, and imperial registers without
+    collapsing them into one universal language?
 
 landed_baseline:
   - Language-neutral state spine.
@@ -162,3 +169,4 @@ landed_baseline:
   - Scratch surface.
   - Schema receipt docs.
   - Rust to Dust setting documentation skeleton.
+  - Eusocial Interbeing naming surface at settings/eusocial-interbeing.
diff --git a/state/scratch.md b/state/scratch.md
index 10c434e..0b885ac 100644
--- a/state/scratch.md
+++ b/state/scratch.md
@@ -14,4 +14,7 @@ rendering structured meaning through an alien ontology and language pipeline.
 - Decide the first artifact format for a language project.
 - Decide whether the first prototype should be notebook-like, CLI-first,
   library-first, or editor/tool-first.
+- Keep Eusocial Interbeing naming work as a setting surface until a real
+  language-project state format exists. Do not mint durable names by translating
+  English labels; decompose meaning and speaker ontology first.
 - Evaluate implementation language after the data model is clearer.