Architecture
The shape of Wavn
Not a diagram of vendors — Wavn deliberately does not discuss what runs beneath it. This page is about something more useful: how the product is shaped, and which rules are enforced in code rather than in policy.
One product, one voice
Whatever is doing the work behind the scenes is Wavn's business. That is not secrecy for its own sake — it is a design decision. The machinery beneath Wavn can change, improve, or be replaced entirely without changing the product you use, the promises it makes, or the way it speaks. You deal with Wavn, and Wavn answers for the whole.
The front door
The chat. It can talk, read and think — and it is honest about the fact that it cannot act. It takes your order, hands it to the parts that do act, and reports what they actually did.
The back room
Where jobs run whole: research, build, check, deliver — in one breath, without babysitting. It is always on, so a long job keeps running after you close the tab.
The cards
Every built file lands in your chat as a card — openable inside Wavn before you keep it. A card is written from the job's real outcome: a failure arrives as a failure, never dressed as success.
The schedule
The part that genuinely acts on time: it sets reminders, moves them, cancels them. Its confirmations are written from the row that came back — which is why they can be trusted.
The mail door
Your Wavn address. It verifies where a message really came from before asking whether the sender is allowed, and turns allowed mail into work — schedule items, builds, answers.
The memory
Projects hold your chats, pages and material. Wavn reads material only inside the project you put it in, and shows its reading — how much, from where, quotable line by line.
Rules enforced in code, not in policy
A rule that lives in a document depends on everyone remembering it. Wavn's rules are enforced by the product itself:
- The kept-promise rule. A confirmation is generated from the record of what happened — the schedule row, the delivered file — never from the intention to do it. The part of Wavn that cannot act says it cannot act.
- The unknown rule. Anything unreadable is rendered as unknown. There is no code path that turns "could not read" into an empty screen.
- The one-voice rule. What Wavn says about itself comes from one written, reviewed source — and the publishing tool refuses to publish that source if internal machinery leaks into it. Wavn cannot drift into describing screens or features that do not exist.
- The no-coming-soon rule. A connection listed before it is built is shown in the present tense, with no button, no date and no "soon." What has no door does not pretend to have one.
- The honest clock. "Built in 14s" is measured from the moment you sent the order — not from some flattering internal moment.
The design bet underneath all of it: trust is an architecture problem. If honesty depends on the model's mood, it will eventually fail. So Wavn's honesty is structural — the checking pass, the record-derived confirmations, the enforced single voice — and the product would rather tell you it failed than convince you it succeeded.
Judge the shape by its output
The architecture is the argument. The finished files are the proof.