Capture Airawa first-contact slice
This commit is contained in:
parent
4a8722a3e2
commit
a1b02edd2d
6 changed files with 144 additions and 3 deletions
|
|
@ -85,3 +85,8 @@ language project can explain the ontology and form.
|
|||
|
||||
See [Language Design Pressure](./language-design.md) for the first Weksa-facing
|
||||
ontology map.
|
||||
|
||||
See [Airawa First-Contact Slice](./airawa-first-contact-slice.md) for the
|
||||
current room consensus on strong Airawa sound, introduction vocabulary,
|
||||
permission-bound dialogue, and why the first chieftain/visitor scene should not
|
||||
be translated as direct English substitution.
|
||||
|
|
|
|||
100
settings/eusocial-interbeing/airawa-first-contact-slice.md
Normal file
100
settings/eusocial-interbeing/airawa-first-contact-slice.md
Normal file
|
|
@ -0,0 +1,100 @@
|
|||
# Airawa First-Contact Slice
|
||||
|
||||
This slice records the room consensus from the first Airawa introduction
|
||||
conversation. It is not a full language project yet. It is a durable pressure
|
||||
note for the first hand-authored Airawa language-project seed.
|
||||
|
||||
## Consensus
|
||||
|
||||
Airawa should sound strong and imposing without becoming decorative noise. The
|
||||
sound should feel deliberate, clipped, and socially heavy: hard stops, closed
|
||||
syllables, dorsal/coronal pressure, and forms that can land like claims rather
|
||||
than flow like scenery.
|
||||
|
||||
The first vocabulary should not begin with random nature nouns. Airawa's first
|
||||
usable words should live where Airawa society puts pressure on speech:
|
||||
|
||||
- identity and standing
|
||||
- formal naming
|
||||
- hearth or origin affiliation
|
||||
- approach permission
|
||||
- border-right and access
|
||||
- peace claim
|
||||
- obligation or sworn bond
|
||||
- gratitude as acknowledged debt
|
||||
- memory-line or lineage record
|
||||
- witness, authority, guest, guard, warrior, hunter, elder
|
||||
- mother-tree access, nutrient gift, surplus, taboo, and delivery through an
|
||||
authorized intermediary
|
||||
|
||||
The language should enter use through social mechanics: who may approach, who
|
||||
may answer, what cannot be asked directly, what must be witnessed, and what
|
||||
obligation is created by accepting a gift.
|
||||
|
||||
## Translation Boundary
|
||||
|
||||
The proposed chieftain/visitor scene is a good first test case, but it should
|
||||
not be translated by substituting English words one by one. A full Airawa
|
||||
rendering is blocked until the project owns at least:
|
||||
|
||||
- a starter lexicon for rank, kinship, place, trade, gift, access, and danger;
|
||||
- a permission model for outsider, host, witness, elder, guard, warrior, and
|
||||
mother-tree access;
|
||||
- grammar for questions, offers, refusals, permission, obligation, honor, and
|
||||
temporal appointment;
|
||||
- a way to distinguish direct speech to a mother-tree from authorized delivery
|
||||
to it;
|
||||
- a rule for whether scars are bodily evidence, honor claims, debt markers, or
|
||||
warrior-status signals.
|
||||
|
||||
Until those are owned, Weksa may produce provisional glosses or placeholder
|
||||
packets, but not claim a clean full Airawa translation.
|
||||
|
||||
## Provisional Seed Evidence
|
||||
|
||||
These forms came from chat and are useful as pressure evidence. They are not
|
||||
canon until a language-project state explains their morphology, phonology,
|
||||
grammar, and allowed usage.
|
||||
|
||||
| Form | Provisional role |
|
||||
| --- | --- |
|
||||
| `atar` | I am / I stand as |
|
||||
| `sakar` | you are |
|
||||
| `qatar` | formal name / name formally |
|
||||
| `daruq` | hearth-origin |
|
||||
| `tazek` | may I approach? |
|
||||
| `kazhar` | I come in peace |
|
||||
| `qerath` | obligation / sworn bond |
|
||||
| `sherek` | gratitude acknowledged |
|
||||
| `ramat` | memory-line / lineage record |
|
||||
| `karuq` | border-right / approach-right |
|
||||
| `thaleq` | witness |
|
||||
| `taruq` | right / authority |
|
||||
| `vezhar` | guest under peace |
|
||||
| `Kaleth` | sample host/chieftain name |
|
||||
| `Serak` | sample visitor/apprentice-warrior name |
|
||||
|
||||
Useful sample frames, still provisional:
|
||||
|
||||
- `Atar qatar Serak.` -- "I stand as formally named Serak."
|
||||
- `Atar daruq ...` -- "I stand from hearth-origin ..."
|
||||
- `Tazek karuq?` -- "May I approach / claim approach-right?"
|
||||
- `Kazhar.` -- "I come in peace."
|
||||
- `Sakar vezhar.` -- "You are guest under peace."
|
||||
|
||||
## First Scene Target
|
||||
|
||||
The first Airawa scene should be a narrow dialogue with speaker locks:
|
||||
|
||||
- host or chieftain asks the outsider's purpose;
|
||||
- outsider gives name, origin, status, peaceful intent, and nutrient-gift offer;
|
||||
- host refuses direct mother-tree access but accepts intermediary delivery;
|
||||
- visitor acknowledges gratitude/debt;
|
||||
- host marks witnessed warrior promise and offers training;
|
||||
- visitor accepts honor and names the scar as evidence;
|
||||
- host appoints a sunrise return.
|
||||
|
||||
This scene is valuable because it forces the language to decide what owns
|
||||
access, obligation, witness, honor, and bodily proof. That is the machine worth
|
||||
building. The word list is only the ash it leaves on the table.
|
||||
|
||||
|
|
@ -34,11 +34,18 @@ Airawa language work must account for:
|
|||
- disconnected tree networks that survived by severing themselves from saturated
|
||||
substrate
|
||||
- imperial labels versus native nation-scale interbeing names
|
||||
- first-contact speech as social mechanics: approach permission, host authority,
|
||||
witness, obligation, gift delivery, taboo access, and accepted guest status
|
||||
|
||||
The Airawa Empire should not be named like a normal state with wet nouns glued
|
||||
on. It is an artificial quarter-continent clausiform exception imposed through
|
||||
biological-memetic control.
|
||||
|
||||
The first Airawa dialogue target is not a generic greeting. It is a
|
||||
chieftain/visitor exchange around mother-tree access, nutrient surplus, guest
|
||||
rights, witnessed warrior promise, and honorable scar evidence. See
|
||||
[Airawa First-Contact Slice](./airawa-first-contact-slice.md).
|
||||
|
||||
### Provisional Airawa Phonology Notes
|
||||
|
||||
Airawa phonology is not finalized, but the current design pressure distinguishes
|
||||
|
|
@ -56,6 +63,13 @@ Provisional tendencies:
|
|||
- avoid making native Airawa names read like smooth Sa'auei'a route names unless
|
||||
the form is explicitly a loan, exonym, or cross-continental register.
|
||||
|
||||
The current room consensus pushes this further for introductory speech: Airawa
|
||||
should sound strong and imposing through deliberate hard edges, clipped or
|
||||
closed syllables, prominent `k/g/q/t/d`, textured `s/z/sh/zh`, and heavy stress
|
||||
on socially important forms. The point is not harshness for its own sake. The
|
||||
point is that claims, permissions, borders, and obligations should land with
|
||||
weight.
|
||||
|
||||
Current scratch name: **Druzkai**, with trilled `r` and `z` pronounced as a
|
||||
voiced postalveolar fricative /zh/ [ʒ]. The name is being considered for a
|
||||
Zyphos Face drawn from a non-imperial Airawa archival/fungal-road tradition: an
|
||||
|
|
|
|||
Loading…
Reference in a new issue