Document utterance embedding handoff
This commit is contained in:
parent
fb79c85250
commit
cbfe9088f9
10 changed files with 217 additions and 179 deletions
|
|
@ -41,8 +41,10 @@ constraints:
|
|||
work. Weksa owns interlingua-to-English projection.
|
||||
- Weksa still owns English pronunciation planning: tokenization, word
|
||||
pronunciations, phrase grouping, stress, and broad IPA stringing.
|
||||
- Long-term speech handoff should use learned line-expression vectors from
|
||||
Weksa and learned synth-control decoding in AquaSynth.
|
||||
- Long-term speech handoff should use Weksa-provided speech text embeddings,
|
||||
prosody/emphasis hints, and Ghostlight/Epiphany-shaped character-state
|
||||
vectors; AquaSynth owns the learned utterance embedding encoder, gradient
|
||||
descent, and synth-control decoding.
|
||||
- Large offline text-embedding jobs should use `bge-m3` on the neighboring
|
||||
Ollama inference box documented in `E:\Projects\gamecult-ops` rather than
|
||||
running on the local Weksa workspace by default.
|
||||
|
|
@ -186,8 +188,9 @@ open_questions:
|
|||
morphology, and diachrony definitions?
|
||||
- What compiled runtime bundle format keeps game-time rendering fast and
|
||||
inspectable?
|
||||
- How should Weksa persist or cache utterance embeddings generated by
|
||||
`bge-m3` on the neighboring Ollama box?
|
||||
- How should Weksa persist or cache speech text embeddings generated by
|
||||
`bge-m3` on the neighboring Ollama box before AquaSynth turns them into
|
||||
utterance embeddings?
|
||||
- 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?
|
||||
|
|
@ -207,8 +210,8 @@ open_questions:
|
|||
- What English G2P path should become executable first: CMUdict lookup plus
|
||||
ARPABET-to-IPA conversion, eSpeak NG oracle comparison, or a trained OOV
|
||||
model?
|
||||
- What dimensionality and training corpus should the first Weksa
|
||||
line-expression encoder use?
|
||||
- What dimensionality and training corpus should the first AquaSynth-owned
|
||||
utterance embedding encoder use?
|
||||
|
||||
landed_baseline:
|
||||
- Language-neutral state spine.
|
||||
|
|
@ -222,7 +225,7 @@ landed_baseline:
|
|||
- Draft flavored-English lowering contract.
|
||||
- Nibu lowering target note.
|
||||
- First English pronunciation plan fixture for Nibu proof output.
|
||||
- First toy line-expression vector fixture for Nibu proof output.
|
||||
- First toy utterance embedding handoff fixture for Nibu proof output.
|
||||
- First Nibu interlingua-to-English lowering fixture.
|
||||
- `bge-m3:latest` installed on neighboring Ollama box `192.168.1.84` and
|
||||
verified through a 1024-dimensional utterance embedding.
|
||||
|
|
|
|||
Loading…
Reference in a new issue