Conversation-aware carriers
Topics, roles, locations, and phrase choices give each visible turn a conversational setting instead of producing isolated text.
Carrier Chat is an inspectable research demo exploring how context-aware text can carry a second, encoded message while still reading like an everyday conversation.
Built for learning. Local phrase banks, server-side breakdowns, and a deliberately honest view of the trade-offs.
A teaching interface for observing selection, payload packing, and decoding—not a claim of perfect invisibility or production-grade security.
The dashboard is designed to make the pipeline easy to inspect, test, and improve rather than hide it behind a black box.
Topics, roles, locations, and phrase choices give each visible turn a conversational setting instead of producing isolated text.
A turn can remain an ordinary message, or carry a small payload for the demo to pack, embed, and inspect.
Send and decode views expose the selected role, slots, payload state, and carrier segments so behaviour can be examined directly.
The direction changed as each failure became useful evidence: reliability, naturalness, efficiency, and privacy all had to be visible in the same demo.
Create a communication system that uses AI to hide an encrypted message inside an ordinary-looking text message.
The original idea combined a normal conversation, a hidden payload, context-aware language, and recipient-only recovery.
If its not possible to encode the secret message into the carrier, throw an error, dont just append repeated text.
That moved the project away from pretending every carrier was successful and toward explicit capacity checks, validation, and visible failure.
What about using a super lightweight offline LLM that can be configured to do this, then all that's needed is a shared secret such as the seed.
The experiment explored local inference, deterministic generation, probability-based selection, and the practical limits of laptop hardware.
fully implement the phrase bank with openai, I dont want to use the statistical method anymore as its too unreliable
The design then shifted toward structured, inspectable language banks with topic and role control instead of relying on fragile model replay.
Make the messages better by not making it lots of short sentences but instead one legit looking long message?
Recent work focuses on coherent conversation, varied roles, local place choices, server-side state, key handling, and language quality that can be evaluated rather than assumed.
No dont use the API. I want you to generate it and upload it to the server for me.
The phrase-bank path is now designed to be locally reproducible, with the source data and generation process kept available for inspection.
This demo sits at the intersection of information theory, cryptography, and linguistic steganography. These references frame the trade-offs around secrecy, detectability, capacity, and reliable decoding.
Register a local account, choose a conversation, and inspect a complete turn from carrier to decoded payload.