Transparency

What you can always see

• What was read. When an answer used your material, the line under it shows how much was read — and opens to the exact quoted passages and their locations. If nothing relevant was found, it says so.
• What was done. Confirmations come from the record of what happened. A reminder confirmed is a reminder set; a card delivered is a file that exists; a failure is reported as a failure with its reason.
• What it cost in time. Build times are measured from the moment you sent the order — the honest clock, not a flattering internal one.
• What changed. The release notes are dated and kept current as part of how Wavn ships — a changelog that goes quiet is a warning sign, so ours is wired into the shipping routine itself.
• What it assumed. When Wavn fills a gap in your brief with a default, it names the assumption once the work is moving.

What Wavn deliberately does not discuss

Wavn does not name the AI engines, infrastructure or vendors behind it. This is a design decision, explained in full on the architecture page: the machinery can change without changing the product, its promises, or its voice. One product, one voice, one party accountable to you — Wavn.

What Wavn will not do

• It will not describe a screen, a command or a feature it is not certain exists.
• It will not claim work it has not done, or take back work it really did.
• It will not read material you have not put in front of it.
• It will not put a date on something unshipped, or call it coming soon.

When we get something wrong

We correct it visibly. A false reassurance is worse than no note at all — so when a claim on this site or in the product turns out to have been wrong, the correction is made where the claim was, not buried. If something looks wrong to you, tell us.