01 / LANGUAGESymbols are input, not the final sentence.
The planned language layer uses modern language models and NLP to translate compact AAC concept sequences into several concise, grammatically correct interpretations. It should understand tense, articles, prepositions, requests, emotion and conversational context while keeping the final choice with the communicator.
02 / VOICECommunication should sound human.
The current browser speech button is only a technology demonstration. The intended product integrates higher-quality speech models and lets the user choose a voice that better represents how they want to sound, rather than treating one synthetic system voice as their identity.
03 / ACCESSHands should not be a requirement.
The full application is planned for a future iOS App Store release. On compatible Apple hardware, the native application is intended to support eye-gaze interaction so people with severe motor limitations can navigate symbols and communicate without dependable hand input. The repository already explores a native SwiftUI/eye-tracking architecture; this capability is not being falsely represented as working in the browser demo.
04 / AGENCYBetter grammar cannot mean changing someone's meaning.
An LLM can generate fluent language that the person did not intend. That is why the system should present interpretations rather than silently rewrite communication. The person remains the author: software expands expression, the user approves what is spoken.
05 / STATUSThis is a development project, not a finished assistive device.
JaredVogler.com demonstrates the interaction model and product direction. The intended destination is a substantially more capable native iOS application with model-backed language humanization, higher-quality selectable speech and hardware-assisted gaze input. Accessibility, privacy, latency and failure-safe behavior remain core engineering requirements before treating it as a production communication aid.