v2.29 Review Flow Clarification

README.md

@@ -2,6 +2,12 @@
 
 [![VSC Conformance](https://github.com/DigiEmu/vsc-core/actions/workflows/vsc-conformance.yml/badge.svg)](https://github.com/DigiEmu/vsc-core/actions/workflows/vsc-conformance.yml)
 
+**Review context:** v2.29 review-flow clarification  
+**Implementation baseline:** v1.x evidence-flow prototype with v2.x review, conformance, and interop documentation  
+**Status:** research prototype / proof-of-concept, not production-ready  
+
+VSC verifies state integrity, not real-world truth.
+
 **v1.18 — Evidence Flow Demo**
 
 Research prototype / proof-of-concept. Not production-ready.

docs/review/VERIFY_FLOW.md

@@ -0,0 +1,49 @@
+# VSC Verify Flow
+
+Status: review-ready documentation note  
+Scope: VSC evidence bundle verification  
+Boundary: `VSC verifies state integrity, not real-world truth.`
+
+## Purpose
+
+VSC checks whether an evidence bundle can be independently reconstructed and compared against declared rules.
+
+It does not make claims about events, decisions, identities, or facts outside the bundle itself.
+
+## Verify flow
+
+1. Load evidence bundle
+2. Read manifest
+3. Check required files
+4. Read declared checksums
+5. Recalculate SHA-256 hashes
+6. Compare expected vs actual checksums
+7. Validate chain / base / delta / metadata references
+8. Classify as PASS / FAIL / ERROR
+9. Emit human-readable and/or machine-readable result
+
+## Result classes
+
+| Result | Meaning |
+|--------|---------|
+| PASS   | Structurally valid and deterministic comparison succeeded |
+| FAIL   | Valid enough to compare, but integrity / checksum / comparison failed |
+| ERROR  | Verification could not be completed due to malformed, missing, unsupported, or unreadable input |
+
+## What PASS does not mean
+
+PASS does not prove:
+
+- real-world truth
+- legal compliance
+- AI safety
+- human identity
+- intent
+- external trust status
+
+## Review boundary
+
+```text
+VSC proves state integrity within a declared evidence bundle.
+It does not prove truth, identity, intent, model safety, policy compliance, or regulatory certification.
+```

examples/interop/tbn-vsc-bundle-001/README.md

@@ -0,0 +1,46 @@
+# TBN / VSC Interop Example Bundle 001
+
+Status: reference example  
+Scope: interop demonstration  
+Boundary: not a formal TBN integration
+
+## Purpose
+
+This bundle demonstrates how an external trust or identity system can reference a VSC evidence bundle without redefining VSC's proof claims.
+
+It shows that an external system may point to VSC artifacts as context without importing or absorbing the VSC proof boundary.
+
+## What this example shows
+
+- bundle structure
+- manifest references
+- checksum verification
+- external-reference boundary
+- deterministic state comparison
+
+## What this example does not prove
+
+- human identity
+- real-world intent
+- legal validity
+- AI safety
+- factual truth
+- TBN trust status
+- production integration between TBN and VSC
+
+## Expected files
+
+| File | Role |
+|------|------|
+| `manifest.json` | Bundle manifest declaring structure and references |
+| `checksums.json` | Declared SHA-256 checksums for bundle files |
+| `base_token.json` | Base state token |
+| `chain_token.json` | Chain token linking base and delta states |
+| `delta_tokens.json` | Delta state tokens |
+| `event_metadata.json` | Event metadata associated with the state chain |
+
+## Usage
+
+Use this bundle to test deterministic verification, checksum comparison, manifest consistency, PASS / FAIL / ERROR behavior, and external-reference boundaries.
+
+Do not use it as a claim of production readiness, certification, or identity proof.