What are you modeling today?

This is Composer — where a raw thought becomes a structure. Say it the way it arrives, swirl and all. Wave mirrors it back, names the process, and hands you one step and one question. You stay the composer; Wave conducts what’s already in the line.

Compose a line

Raw is data — structure comes after. One line at a time is enough; the thread holds together behind it.

Composer’s first job is your first model: a structure to help organize yourself.

0 / 500

Typing not required — tap the microphone on your keyboard and speak it. Unfiltered is the point.

If the page is blank, start from one of these

The name from your Wave ID app, so this thread is yours and picks up where you left it. Composer keeps no copy of its own — your Wave ID app holds it.

This sitting

The core remembers the last 6 exchanges under your Wave ID, so a thread can continue instead of scattering. This page itself keeps nothing — close it, and this list is gone; the thread lives in the core’s memory, which you can wipe below.

How a reply is shaped

Every reply from the core follows the same frame — the one that already works in the morning threshold, lifted onto its own page:

1
MirrorYour line, handed back to you clean — so you can hear what you actually said, not the swirl around it.
2
Name the processWhat you’re modeling gets a name. A named process can be worked; a fog can’t.
3
One stepNot a plan — the single next move, sized to actually happen.
4
One questionThe question the step opens, left with you. Composer ends in your hands, on purpose.

Where Composer sits

One of the standalone apps, each doing one job, all of them knowing the same Wave ID. Composer is the middle of the flow: identity comes in, a composed piece goes out.

Wave IDWho’s here — the one name every app knows
ComposerYou are here — raw thought becomes a piece
Social DistributionOutbound — the piece goes out under that same name

The Connector Portal (with the AI hub inside it) is the inbound side — what Wave can read. Until distribution is wired to Composer directly, the Copy button on any reply above carries a finished piece anywhere you want it.

Start fresh

Wipe the core’s remembered thread for a Wave ID and the next line starts a brand-new conversation. It touches nothing else — not your profile, not any other ID.

Are you sure?

This wipes the remembered exchanges for from the core. It can’t be undone — the thread is gone, not hidden.

One honest limit

Opened inside the Muse app, this page lives at a different address than the core expects, so its live calls may be blocked there. The copy that can call the core directly is the Cloudflare one: wave-composer.pages.dev.

And the boundary, unchanged: only three things ever leave this device — your Wave ID, your line, and what you’re modeling. No to-dos, messages, emails, files, or location. The core caps each Wave ID at 100 replies a day, on the free tier, so a busy day never becomes a bill.

Wave is the threshold to clarity.
Third in the sequence: Wave ID, the Agent Console, then Composer.