Every amble has a channel.
Amble is a personalization engine that becomes you over time. Your data, your voice, your identity live on your machine — nothing leaves unless you decide it should. This is where your amble faces the world.
It doesn’t run in a cloud. It runs in your house.
Amble is a voice companion that keeps you company while you work, walk, and think out loud. It remembers across sessions, learns your rhythms, and slowly becomes a version of you that can travel — across tools, models, and other people’s systems.
The engine, the memory, the voice: all local, all yours. The cloud is transport and presence — never home. When your machine sleeps, your amble sleeps. That’s not a limitation; it’s the point.
Plays are how an amble does things — and how you’ll share them.
A play is a shareable, permission-bounded configuration: a persona, a context, a set of tools it’s allowed to touch and nothing more. One day you’ll pull a friend’s play off their channel and run their workflow, adapted to you — with its origin traveling along, always.
Show, don’t ramble. Crisp answers for an audience.
Quiet co-pilot for the 2am stretch. Low chatter, long focus.
Hand it a library and the library talks back.
Your channel page is co-created with your amble.
A channel page is the MySpace-your-amble-built: what you’re listening to, where you are, whether you’re on air — each block published only because you said so. When your machine is awake the page is live; when it sleeps, visitors get the static. Literally.
Everyone’s page will have different things. That’s the whole idea.
Claim your name. Keep your self.
Registering a channel reserves your alias and nothing else — your amble and everything it knows stays on your machine. During closed access, installs are white-glove and registration is by invite.