Proof-of-Action - Enterprise Verification Guide

This guide mirrors VERIFICATION_GUIDE_ENTERPRISE.md shipped inside every Proof-of-Action bundle. Paste the full bundle JSON at verify.aevesa.com to open the Verification Dashboard - manifest RS256 and file_integrity run in your browser only.

1. What you are proving

Layer	Artifact	Meaning
Primary	ledger/anchor.json	Action recorded on Aegis ledger (`aegis/1` entryHash).
Secondary (MCP)	mcp/*	Human/policy gate authorized tool + args digest.
Secondary (Forensic)	forensic/session_chain.json	Hash-linked MCP session narrative + session_digest.

MCP and forensic artifacts validate intent; they do not replace the ledger anchor.

2. Policy Drift flag

In forensic/session_chain.json:

"policy_drift": {
  "policy_context_stable": false,
  "distinct_policy_hashes": ["abc…", "def…"]
}

policy_context_stable: true - Every hop used the same policy_version_hash.
policy_context_stable: false - Policy hash changed between hops. Correlate distinct_policy_hashes with change-management and policy/snapshot.json.

session_digest is SHA-256 over ordered hops; tampering changes the digest.

3. Recommended verification order

Manifest RS256 + file_integrity (browser or offline).
entry_hash_verification on primary anchor.
mcp_intent_witness in manifest proof chain.
forensic_session_chain when applicable.
Optional: POST /api/v1/public/verify-receipt merkle_proof mode.

4. Abandoned HITL

Export returning BUNDLE_INCOMPLETE means no Mongo HITL_APPROVAL_RELEASE seal - pending Prisma rows are not proof of release.

5. Privacy

Bundles redact prompts, tokens, and raw tool args. Verification uses digests and JWS only.