A clear check before “done.”

Start with a tiny made-up project. See what was promised, what changed, and why the checker returned that result. Then adapt the files with your own coding assistant.

Offline guide · No account · No code upload · All examples are synthetic

Try the free example See what you need first

Keep the first run separate.

Unpack the whole download. Keep it outside your real project.
Open this guide. Nothing executes just by reading it.
Use Python 3.12+ with exactly INVARA 0.2.0 in a fresh environment, or ask your local coding assistant to set that up.
Run a synthetic example. Read the original result before adapting anything.

Open instructions to give your assistant · Read the full setup notes

Show the Windows setup and first run

py -3.12 -m venv .venv
.\.venv\Scripts\python.exe -m pip install invara==0.2.0
.\.venv\Scripts\python.exe run_example.py feature

Installation needs a public 0.2.0 package or the official sealed wheel. If unavailable, stop rather than substitute a different download. The examples themselves are local. Python commands run with your permissions; this is not a sandbox.

Producer example execution: Windows / Python 3.12.10. Linux example execution and macOS/editor installation are not claimed by this kit. Independent review is separate from the producer record.

Workflow 1
Protect agreed checks

Add the feature. Keep the promise.

The made-up greeting program already greets one name. Add a greeting for several names while leaving the agreed check files unchanged. The plan is recorded before the change.

Synthetic example · Expected result, not your project's verdict

Promise: keep two agreed check files unchanged.

Observation: the feature is added; both checks run; their protected bytes stay the same.

Checked conditions met · PASS

Only those two checks and protected files are covered. General correctness, security and customer projects are not checked.

Now try the changed-file variation. The feature still works, but a comment is added to a protected check after the plan was recorded. That breaks the declared condition, so the expected result is BLOCK.

Show both complete example commands

python run_example.py feature
python run_example.py feature --case changed

Use the Python inside your fresh environment. Each run creates a new folder. The changed-file example exits with 1 because its actual verdict is BLOCK; that is the expected teaching result, not a PASS.

Read the complete workflow · Open the editable task plan

When you use your own project

Ask your assistant to identify the actual files to protect and the existing commands that provide useful evidence. Read the explanation and commands before sealing. If a usable before state or check is missing, name the gap. Do not invent a successful result.

Read the result. Keep the unknowns.

Original result	Next step
PASS	Read the tested scope and limits. Decide whether more evidence is needed.
BLOCK	Read the broken condition or observed difference. Keep the original record.
UNVERIFIABLE	Restore the missing prerequisite. Unchecked is not passed.
HUMAN_REVIEW	A person must review the stated issue. Exit code zero does not make it PASS.
REFUSED or runner error	The operation did not finish as a usable verdict. Read the reason and local receipt.

Open common problems and recovery steps · Read the synthetic producer outcome summary

Yours to reuse.

This complete feature example is free. No payment, account or paid kit is required. The checker and its public documentation remain free.

The newly authored material uses the permissive MIT License. INVARA remains a separate free Apache-2.0 package and is not bundled in this download. No subscription, runtime service or license activation is added.

Read the license · Read what is included · Read the privacy notes

To recommend it, share the free-example page at migaryos.com/invara/. Do not attach your project evidence or a purchase link with private identifiers.