#How Nourva checks its work
When Nourva tells you something is done, it has already confirmed the result is real.
#Overview
Nourva does more than attempt a task — it checks the outcome before it tells you the task is finished. Every action Nourva takes is automatically verified before it is reported as done. If a step does not actually succeed, Nourva notices it, says so honestly, and retries or adjusts instead of claiming a result it did not get.
This is the foundation of trusting Nourva with real work. A "done" is not a hopeful guess or a step that was merely tried; it means the outcome was confirmed. Because this checking happens automatically on every task — across Chat, Arachne, the Shell, Office, and every other surface — you can hand off a goal and rely on the result you are shown.
#What verification means
- Every action is checked. Nourva confirms that each step did what it was supposed to do before moving on or reporting back.
- Honesty when something fails. If a step does not succeed, Nourva tells you plainly rather than pretending it worked. You always know the real state of your task.
- Retry and adjust, not pretend. When Nourva catches a failed step, it tries again or takes a different approach toward your goal instead of papering over the gap.
- A trustworthy "done." Nourva never reports a task as finished unless it has confirmed the actual result. "Done" carries weight because it is earned.
- Verified results you can reuse. What Nourva hands back — a document, a piece of research, a built site, a result in any of the eight formats — is something that was confirmed before it reached you.
#How to use it
Verification is automatic. You do not turn it on, configure it, or ask for it — it is simply how Nourva works on every task. To get the most from it:
- Describe the outcome you want. Tell Nourva the result, in plain language. The clearer the goal, the more precisely Nourva can confirm it was met.
- Trust a reported "done." When Nourva says a task is finished, the result has been checked. You can move on without re-confirming the basics yourself.
- Read an honest failure as a real signal. If Nourva says a step did not succeed, that is the true state of things — use it to decide whether to adjust the goal, give more freedom, or step in.
- Watch the work when you want certainty. On surfaces where the work is visible — such as Arachne and the Shell — you can watch it happen live and see verification play out step by step.
#Examples
You ask:
Fill out this application form for me and submit it.What you see: Nourva completes the form and confirms the submission actually went through before telling you it is done — not just that it pressed the button, but that the process finished.
You ask:
Research the top options in this space and give me a comparison.What you see: a comparison you can trust, because Nourva confirmed it gathered and read real sources before presenting the result — with the sources gathered into a source pack you can check.
You ask:
Build me a small site that does this, and make sure it works.What you see: a site you can open and use, reported as done only after Nourva confirmed it actually works — and if something did not come together, Nourva tells you so and adjusts rather than handing you something broken.
#Tips
Treat a "done" from Nourva as a verified result, not a promise. That is exactly what it is designed to mean.
- When you want to see verification in action, choose a surface where the work is visible and watch the first run — you will see Nourva check each step before it continues.
- An honest "this step did not succeed" is a feature, not a setback. It saves you from acting on a result that was never real.
- For long, well-understood tasks you trust, you can give Nourva more freedom and rely on verification to keep each step honest along the way.
- Pair verification with the permission levels: lower levels keep you in the loop for each change, while verification quietly confirms every action regardless of the level you choose.