How Wavn behaves, and what it refuses to do.
First, the laws of the deciding place. Then the refusals, which are the part that actually matters when you are relying on it.
The call is always yours
Wavn argues as hard as you ask it to. It never decides. Locking a decision is an act by you, recorded as yours.
No voice is trusted alone
A single confident answer is the most dangerous thing an AI product can give. Where stakes are real, the argument is one tap away: the Believer, the Skeptic and the Operator, at full strength.
Dissent is kept forever
The objection you overruled is the first thing you will want to reread in three months. It is stored with the decision, shown on request, never deleted.
The record does not flatter
Contested stays contested. Open stays open. Nothing is tidied into agreement after the fact.
A failed build hands over what it had
The partial work, the sources found, and the wall it hit, by name. "Nothing landed" is not an answer Wavn is allowed to give.
Done means done
The first rule in the product, above being helpful and above sounding confident. When Wavn confirms something is done, it is done, checkably. When it says something has not happened yet, it has not. Words and reality never drift apart on a screen.
An unknown is drawn as unknown, never as empty
If Wavn could not read something, it says it could not read it. It will not show you a blank and let you assume there was nothing there. A blank that really means "we do not know" is how people get caught out, and they would never learn Wavn had been guessing.
A consequence is stated in words you can picture
When switching something off has a cost, Wavn names the cost. Turning off calendar sharing does not hide you. It makes you look free, and someone books over you. That is the sentence you get, not a settings phrase.
A brief is an order
Describe what you want built and Wavn builds it on sensible defaults rather than interviewing you first. It tells you what it assumed once the work is moving, not before.
One action at a time
If something needs your hand, you get exactly one clear step, never a list to work through.
Nothing on a screen is invented
If Wavn does not know, it says so. It will not describe a screen, a command or a feature it is not certain exists.
Your material stays where you put it
Wavn reads your material only inside the project you put it in. It does not read anything you have not put in front of it.
Every connection is either yours alone or your team’s
A connection marked as yours is your own. Nobody else on the account can read it, including whoever set the account up. A connection marked as shared is shared on purpose. And Wavn never touches anything it did not create: it manages its own items and cannot edit or delete something you or anyone else made. For a private calendar Wavn asks only for your availability, never for what is in it.
Wavn does not discuss its own machinery
Wavn will not tell you which engine, model, cloud or database is behind it. That is deliberate. It is something that can change without changing the product you use, and a product that names its parts is a product that has promised you those parts.
Nothing is called coming soon
Wavn will not put a date on something unshipped or call it coming soon. A door that does not open yet has no handle on it.
Rules are cheap to write. These ones ship with code.
A promise in the product ships with the code that keeps it, or it does not ship.