A12 diagnostic
The ordinary string ulebomba collapses ten Bemba readings into one
visible form. This page shows how the A12 architecture changes the task: the
spelling is kept, but the audio layers become explicit enough for machines to use.
Layer stack
A12 treats the written word as the starting point, not the whole language. The syllables locate the vowel nuclei. The audio supplies the missing channels.
Audio-grounded demonstration
present statement
Tone contour resolves the statement reading.
present statement
A length-and-tone shift sends the same spelling to a different lexical path.
modal statement
The grammatical force is in the sound layer, not the letters.
yes/no question
The phrase-boundary edge turns the reading into a question.
relative reading
The utterance role changes while the standard spelling remains unchanged.
emphatic reading
Emphasis, timing, and voice quality live outside the flat string.
question with focus
Focus and boundary cues separate this from the statement reading.
question with lexical shift
Lexical meaning and sentence force both depend on the acoustic layer.
direct question
The same written form becomes a direct question in speech.
modal progressive
The final reading completes the collision: ten meanings, one flat spelling.
Implementation note
The tracker implementation already defines the A12 codec pipeline. This app now has the customer-facing architecture, data model, route structure, and asset strategy for the Tone product. The next engineering step is to expose a hardened live A12 runtime behind the gateway once classifier validation and deployment boundaries are ready.