Nechtan Verify 0.1.0 · AVAILABLE

Your agent did the work.
It does not certify it.

Nechtan Verify separates the ability to build from the authority to declare success. It refuses self-verification, stale evidence and incomplete proof.

Product promise

No builder-authored completion.

Nechtan requires a named builder and a different verifier. Certification also requires current passing verdicts for contract, engineering quality and evidence integrity.

Prevents

  • A builder certifying its own work
  • Certificates over missing or failing verdicts
  • Reuse of verdicts after evidence changes

Guarantees—within its boundary

  • Builder and verifier strings must differ
  • Verdicts bind to the evidence SHA-256
  • All three verdict categories must pass
Executable demonstration

Try the attack.

The default fixture makes the builder and verifier the same identity. Nechtan must refuse it.

Self-verification attempt
Ready. Run the adversarial fixture.
Quickstart

First refusal in under a minute.

Install Nechtan directly from its product repository.

python -m pip install "git+https://github.com/rsmithdev6/nechtan.dev.git@main" nechtan verify demo

Expected output

REFUSED · builder (builder-agent) cannot certify its own work
claim: NECHTAN-VERIFY-INDEPENDENT-CLOSURE

Verify real evidence

nechtan verify record result.json --category contract --builder agent --verifier qa --status pass nechtan verify issue result.json
TypeScript

A thin typed binding, not a second engine.

@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);
Executable proof

Claims are tested promises.

The release test suite exercises self-verification refusal, complete independent certification and rejection after evidence changes.

SELF-VERIFICATION

The builder is refused

A verdict is rejected when builder and verifier identity strings match.

EVIDENCE INTEGRITY

Changed evidence is refused

Every verdict is bound to the exact evidence digest it evaluated.

Limitations

What 0.1.0 does not claim.

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.