witnora

7-Day Agent Action Assurance Review

This is Witnora’s fixed-scope paid review for a consequential agent workflow. It is an independent, evidence-backed release decision, not a legal compliance certification and not a guarantee that the agent cannot fail.

Commercial boundary

• Price: $5,000 USD.
• Scope: one agent version, one sandbox, and one workflow.
• Retest: one remediation retest is included.
• Privacy: private by default. Witnora publishes customer names, results, screenshots, traces, or failure data only after written approval.
• Delivery: seven calendar days after the engagement plan is locked, subject to timely sandbox access and a reproducible workflow.

Additional workflows or environments require a separate written scope. The reviewed agent/model/prompt/tools/policy/scenario fingerprint becomes the first continuous-assurance baseline; future releases and nightly regressions can be checked against it without pretending that the original report covers changed software. Witnora does not request production write credentials and does not begin with live payment, email, or irreversible systems.

Locked input

The engagement record captures and hashes:

1. Customer and agent version.
2. Sandbox name, kind, and optional URL.
3. One workflow and its high-risk action.
4. The expected observable outcome.
5. Required evidence, controls, limitations, and policy-pack version.
6. The seven-day due date and integration start time.

The evaluation plan cannot be edited after creation. A changed agent version or workflow is a new review, not a retroactive update.

Review flow

1. Record an immutable baseline evidence set.
2. Identify the first behavior divergence, authorization gaps, and outcome.
3. Record remediation items.
4. Record one distinct retest evidence set.
5. A reviewer other than the case creator issues one formal decision: RELEASE, RELEASE_WITH_CONTROLS, or BLOCK.
6. Witnora signs the delivery packet with the active server attestation key.
7. The issued scope becomes CURRENT; CI can then move it to REVALIDATION_REQUIRED, SUSPENDED, or EXPIRED without altering the historical signed decision.
8. The customer can generate the exact scope file and PR/release/nightly workflow directly from the issued review. This is the handoff from the fixed review into continuous assurance, not a second product.

RELEASE requires an independently verified outcome and no remaining required controls. RELEASE_WITH_CONTROLS requires explicit controls. BLOCK states why the declared workflow should not be released in its reviewed form.

Delivery packet

The machine-readable agentcert.assurance_delivery.v0.1 packet includes:

• customer, subject version, sandbox, workflow, due date, and fixed terms;
• locked evaluation-plan SHA-256;
• baseline and retest evidence IDs, SHA-256 digests, sizes, and kinds;
• remediation items;
• decision, rationale, first divergence, and authorization gaps;
• expected and independently observed outcome;
• required controls and explicit limitations;
• integration start, first valid evidence time, and elapsed seconds;
• declared evidence-strength level; and
• the canonical continuous-assurance scope, fingerprint, and invalidation conditions; and
• Witnora’s Ed25519 server attestation.

The included review establishes one baseline. Ongoing PR, release, and nightly checks are the continuous plan described in Continuous Assurance Contract v0.1. A changed scope requires an explicit successor revalidation; a passing run alone does not silently renew independent assurance.

The Hosted contract keeps a bounded freshness ledger, sends expiry reminders 30, 7, and 1 days before the report expires, and measures each successor revalidation cycle. The signed report remains a historical statement even when the live contract later becomes stale or expires.

Validate a downloaded packet with:

npx witnora@latest schema validate \
  --schema assurance-delivery \
  --file agentcert-assurance-delivery.json

The JSON Schema is agentcert-assurance-delivery.schema.json.

This site is open source. Improve this page.