Oktsec Node: recorded action-evidence verification examples
Executed September 9, 2026. Synthetic test data, no customer records.

Source fixture: commercial oktsec-node/internal/node/action_evidence_bundle_v1_fixture.json.
Verifier: commercial Oktsec Node, verify action-evidence command.
The public open-source Oktsec CLI is a separate distribution.

Original: intact.json, two batches and four receipts. Exit 0, valid and complete.
Altered: altered.json, first receipt resource_id changed from server/tool to server/tooL,
without re-signing. Exit 4, validity fails.
Incomplete: incomplete.json, final batch removed and selection metadata adjusted.
Exit 6, included signatures are valid but the action lifecycle is incomplete.

Each *-result.json is the verifier's recorded JSON output for that input.
No verification executes in the browser. No binary or private signing key is provided.

Using your commercial Node verifier:
oktsec verify action-evidence --file intact.json --expected-node-fingerprint sha256:e6eb8e3b4fc293f9073166de45d798451952f986fa25109eb847a1c68a78a16b --json

That fingerprint belongs ONLY to this synthetic fixture. For actual evidence,
obtain the enrolled node fingerprint through an independent trusted channel.
Coverage assurance for these fixtures is included_batches_only. Integrity and
lifecycle checks cannot establish that every batch or every action was exported.