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.

Whenever a completion verdict is recorded, Nechtan Verify requires a known builder and a distinct verifier. A completion certificate also requires current passing verdicts for contract, engineering quality and evidence integrity.

Prevents

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

Guarantees—within its boundary

  • Identity separation is enforced by the closure engine
  • Verdicts bind to an exact evaluation hash
  • All three named 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 the current Nechtan distribution, then invoke the public wrapper over the canonical closure engine.

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

Expected output

REFUSED builder (builder-agent) cannot record its own contract verdict
claim=CLAIM-THREE-VERDICT-CLOSURE

Canonical CLI mapping

nechtan verify record OBL-ROOT --category contract --verifier qa --status pass nechtan verify issue --contract OC-1 --root OBL-ROOT
TYPESCRIPT

A thin typed binding, not a second engine.

@nechtan/sdk builds the canonical Nechtan CLI contract and accepts your host executor. Policy and certificate authority remain in the Python runtime.

import { Nechtan } from "@nechtan/sdk"; const command = Nechtan.verify.record({ obligationId: "OBL-ROOT", category: "contract", verifier: "qa", status: "pass" }); const result = await Nechtan.verify.execute(localExecutor, command);
CANONICAL PROOF

Claims are executable promises.

This public product is bounded by two verified claims in config/claims.json.

CLAIM-ADVERSARIAL-COMPLETION

Illegal closure routes refuse

Sixteen adversarial fixtures cover missing coverage, stale proof, self-review, scope drift and unchanged retry.

CLAIM-THREE-VERDICT-CLOSURE

Three current verdicts required

A missing, failing, stale or builder-authored verdict blocks certification.

LIMITATIONS

What 0.1.0 does not claim.

Identity strings are supplied by the host; Nechtan Verify enforces separation but does not by itself prove the real-world identity behind a string. The initial TypeScript surface is a local CLI binding. Hosted verification and managed identity are not part of this release.