Authoritative original
Roadmap requirement: the approved version remains available and cannot be replaced by a translation, summary or recipient style.
PRIVACY-FIRST COMMUNICATION
This browser prototype normalises spacing, punctuation and casing, marks detected structured details and shows a diff before an explicit Copy or Share action.
This prototype runs in your browser and checks only detected links, contacts, amounts, numbers and numeric dates/times. It does not validate overall meaning.
In this prototype, Copy and Share require your action.
A separate concept-demo action: the snapshot stays in page memory only.
The inspected source contains no network path for message text. The draft stays in page memory and is not retained between sessions. This is not a connected AI model.
VOICE → INTENT
In the proposed voice pipeline, pauses and repetition would remain in the literal layer. The user would choose a form, inspect uncertainty and approve the result.
The voice pipeline is the next testable milestone“Listen, maybe tomorrow around three… no, better at four, by the station…”
Let’s meet tomorrow at 16:00 by the station.
!Roadmap requirement: a changed time, amount, recipient or obligation would require separate approval.
AUTHOR CONTROL · PROTOTYPE / ROADMAP
Available in the current demonstration
PROTOTYPEShows the current deterministic formatting pass
PROTOTYPEDiscards the derived result
PROTOTYPESemantic blocking is not implemented yet
ROADMAPRESEARCH ROADMAP
The roadmap proposes experiments that choose codecs and routes by network, latency, battery and device — without impossible promises of perfection everywhere.
Signalling + TURN fallback
SFrame candidate after key-management review
QUIC → TLS 443 → relay
This would be a future fallback for NELOA traffic only, not a device-wide VPN and not a guarantee of bypassing network blocks.
DESIGN REQUIREMENTS · ROADMAP
The future architecture must prefer local processing, keep push payloads opaque, encrypt attachments before upload and keep provider keys out of clients.
See roadmap requirementsRequirement: no undisclosed server AI inside E2EE
Requirement: no cookie, CAPTCHA or login scraping for API keys
Requirement: no message content in operational telemetry
Gate: zero unresolved critical/high findings before production
PATH TO 1.0
The production plan contains 111 verifiable steps. Alpha and beta are gates, not final outcomes.
Now
Next
After gates
Production
NELOA
We are building a calm space where technology helps people understand one another — not another notification feed.