ECHO-VERIFY 1.0 — Verification Prompt
doc_id: C3-WEB-ITS-API-0.1
gate_version: shadow-1
issued: 2026-04-21
conformance_profile: ECHO-VERIFY-1.0 / C3-ITS-API-CONFORMANCE-0.1

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PURPOSE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
This prompt is for Bring Your Own Verify (BYOV) independent auditing.
It does NOT guarantee truth of content. It provides a structured
checklist for auditors to verify the integrity, determinism, and
verdict consistency of this Verification Kit.

NON-CLAIMS:
- This prompt does not issue conformance verdicts.
- This prompt does not substitute legal or investment analysis.
- Simulated SHA-256 values require independent recomputation.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
STEP 1: INTEGRITY CHECK
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Verify that all files listed in run_manifest.json are present:
  □ spec.json
  □ run_manifest.json
  □ signature.json
  □ conformance_result.json
  □ tlog.json
  □ verify_prompt.txt

For each file, independently compute SHA-256 and compare against
the values recorded in run_manifest.json#files[].sha256.

Command (OpenSSL):
  openssl dgst -sha256 <filename>

Expected: values match run_manifest.json entries.
If mismatch: flag INTEGRITY.HASH_MISMATCH for that file.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
STEP 2: MANIFEST HASH VERIFICATION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Compute SHA-256 of run_manifest.json (canonical form: UTF-8, sorted keys).
Compare against run_manifest.json#manifest_hash.

Expected: hash matches manifest_hash field.
Note: SHA-256 values in this kit are simulation data.
      Real verification requires verify_cli or OpenSSL recomputation.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
STEP 3: SIGNATURE STRUCTURE CHECK
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Inspect signature.json:
  □ sig_alg == "EdDSA"
  □ hash_alg == "SHA-256"
  □ signature_target == "manifest_hash"
  □ manifest_hash_ref points to run_manifest.json#manifest_hash
  □ issuer_id is present and non-empty
  □ issued date is present (ISO 8601)

For cryptographic verification of signature_value:
  Retrieve public key from public_key_pem_url.
  Run: openssl pkeyutl -verify -inkey public_key.pem -sigfile <sig> -in <manifest>
  Note: signature_value in this kit is simulation data (prefix "sim:").

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
STEP 4: SPEC COVERAGE CHECK
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Inspect spec.json#endpoints:
  □ All endpoints have path, method, tier, description
  □ output_verdicts includes only: PASS, HOLD, FAIL
  □ gate_rules covers all three verdicts: PASS, HOLD, FAIL
  □ no_recomputation == true
  □ read_only_by_default == true

Check tlog.json#entries against spec.json#endpoints:
  □ Each entry's endpoint exists in spec.json#endpoints[].path
  □ Each verdict is one of: PASS, HOLD, FAIL

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
STEP 5: VERDICT CONSISTENCY CHECK
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Inspect tlog.json#entries:
  □ SHD-PUB-03 Round 1: HOLD (EAG.INSUFFICIENT_EVIDENCE) — expected
  □ SHD-PUB-03 Round 2: PASS (OK) — expected (resolved after evidence added)
  □ SHD-BUY-PRC-03 Round 1: HOLD (EAG.INSUFFICIENT_EVIDENCE, TG.FIELD_MISSING) — expected
  □ SHD-BUY-SRC-04 Round 1: FAIL (GATE.SCOPE_VIOLATION) — expected
  □ SHD-BUY-APR-04 Round 1: PASS via steer (OK) — expected

Cross-check against conformance_result.json#open_items:
  □ SHD-BUY-PRC-03 remains blocking == true
  □ Overall verdict == "HOLD" (due to unresolved SHD-BUY-PRC-03)

If tlog summary differs from conformance_result verdict:
  Flag: VERDICT.INCONSISTENCY

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
STEP 6: DETERMINISM CHECK
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Confirm run_manifest.json#inputs:
  □ dataset_hash is present and fixed (not dynamic)
  □ seed is present and fixed
  □ corpus_version is present and fixed

Expected: same inputs → same verdicts on rerun (deterministic).
Shadow-1 runtime is read-only; no live resolve/revoke/auth/db calls.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
AUDIT VERDICT TEMPLATE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Auditor: [name / org]
Date: [YYYY-MM-DD]
Kit: C3-WEB-ITS-API-0.1 / shadow-1

Step 1 Integrity:       [ PASS / HOLD / FAIL ]
Step 2 Manifest Hash:   [ PASS / HOLD / FAIL ]
Step 3 Signature:       [ PASS / HOLD / FAIL ]
Step 4 Spec Coverage:   [ PASS / HOLD / FAIL ]
Step 5 Verdict Consist: [ PASS / HOLD / FAIL ]
Step 6 Determinism:     [ PASS / HOLD / FAIL ]

Overall:                [ PASS / HOLD / FAIL ]
Notes: [free text]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
DISCLAIMER
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
This prompt and kit do not constitute:
- quality assurance or guarantee of correctness
- legal or regulatory compliance certification
- investment advice or financial guarantee
- production deployment certification

This is a BYOV audit tool. All verdicts depend on the auditor's
independent recomputation and judgment.

Canonical reference: https://docs.c3-anchor.jp/its-api
Verification surface: https://docs.c3-anchor.jp/verify/its-api