Prevents
- A builder certifying its own work
- Certificates over missing or failing verdicts
- Reuse of verdicts after evidence changes
Nechtan Verify separates the ability to build from the authority to declare success. It refuses self-verification, stale evidence and incomplete proof.
Nechtan requires a named builder and a different verifier. Certification also requires current passing verdicts for contract, engineering quality and evidence integrity.
The default fixture makes the builder and verifier the same identity. Nechtan must refuse it.
Ready. Run the adversarial fixture.
Install Nechtan directly from its product repository.
python -m pip install "git+https://github.com/rsmithdev6/nechtan.dev.git@main"
nechtan verify demoREFUSED · builder (builder-agent) cannot certify its own work claim: NECHTAN-VERIFY-INDEPENDENT-CLOSURE
nechtan verify record result.json --category contract --builder agent --verifier qa --status pass
nechtan verify issue result.json@nechtan/sdk builds typed commands for the installed Nechtan runtime.
import { Nechtan } from "@nechtan/sdk";
const command = Nechtan.verify.record({
evidence: "result.json", category: "contract",
builder: "agent", verifier: "qa", status: "pass"
});
const result = await Nechtan.verify.execute(localExecutor, command);The release test suite exercises self-verification refusal, complete independent certification and rejection after evidence changes.
A verdict is rejected when builder and verifier identity strings match.
Every verdict is bound to the exact evidence digest it evaluated.
Identity strings are supplied by the host; Nechtan enforces separation but does not authenticate the real-world identity behind a string. The TypeScript surface is a command binding. Hosted verification and managed identity are not included.