Add VSC v2.28 partner-facing review brief

Author: DigiEmu

README.md

@@ -65,6 +65,8 @@ Partner / reviewer interop brief: [`docs/interop/PARTNER_REVIEWER_INTEROP_BRIEF.
 
 Enterprise review package: [`docs/review/ENTERPRISE_REVIEW_PACKAGE.md`](docs/review/ENTERPRISE_REVIEW_PACKAGE.md). Review package only; not certification. Includes validation commands, expected outputs, key files, and explicit non-claims.
 
+Partner-facing review brief: [`docs/review/PARTNER_REVIEW_BRIEF.md`](docs/review/PARTNER_REVIEW_BRIEF.md). Short PDF/source-friendly entry point; not certification.
+
 ## CI Conformance Check
 
 VSC includes a GitHub Actions workflow for automated conformance validation.

docs/releases/v2.28-partner-facing-review-brief.md

@@ -0,0 +1,91 @@
+# VSC v2.28 — Partner-Facing Review Brief / PDF Source
+
+Release: v2.28  
+Project: DigiEmu VSC / VSC Core
+
+## Summary
+
+VSC v2.28 adds a compact partner-facing review brief.
+
+The brief is designed as a short entry point for partners, reviewers, research institutions, accelerators, and due-diligence readers.
+
+It can also be used as a PDF source.
+
+## Added
+
+New review document:
+
+```text
+docs/review/PARTNER_REVIEW_BRIEF.md
+```
+
+## Purpose
+
+The brief explains:
+
+- what VSC is
+- what is review-ready
+- which reproducibility commands to run
+- how PASS / FAIL / ERROR should be interpreted
+- what the interop model means
+- what external references do not mean
+- what VSC does not claim
+- what a useful next review step could be
+
+## Important status
+
+This is a partner-facing review brief.
+
+It is not certification.
+
+v2.28 does not add:
+
+- verifier logic
+- CLI commands
+- CI workflow changes
+- fixture files
+- fixture validation
+- schema changes
+- external reference validation
+- external artifact validation
+- integration-complete claims
+- v3.0 start
+
+## Core positioning
+
+```text
+Review-ready, not certified.
+```
+
+Core proof boundary:
+
+```text
+VSC proves state integrity, not truth.
+```
+
+## Updated
+
+- README review links
+- Enterprise review package cross-reference
+
+## Unchanged
+
+v2.28 does not change:
+
+- Go verifier behavior
+- Node runner behavior
+- CI workflow behavior
+- conformance fixture expected results
+- external reference schema semantics
+- PASS / FAIL / ERROR technical meaning
+- evidence bundle verification logic
+
+## Release meaning
+
+v2.28 turns the enterprise review package into a shorter partner-facing entry point that can later be exported as a PDF.
+
+## Next possible step
+
+```text
+Partner email / PDF export / v3.0 architecture review / reporting plan
+```

docs/review/ENTERPRISE_REVIEW_PACKAGE.md

@@ -381,6 +381,16 @@ Open risks:
 Recommended next steps:
 ```
 
+## Partner-facing brief
+
+A compact partner-facing review brief is available in:
+
+[`docs/review/PARTNER_REVIEW_BRIEF.md`](PARTNER_REVIEW_BRIEF.md)
+
+It is designed as a short entry point or PDF source.
+
+It is not certification.
+
 ## Summary
 
 VSC Core 2.x is structured for technical and governance review.

docs/review/PARTNER_REVIEW_BRIEF.md

@@ -0,0 +1,272 @@
+# Partner Review Brief
+
+Project: DigiEmu VSC / VSC Core  
+Release context: v2.28  
+Status: partner-facing review brief / PDF source
+
+## Purpose
+
+This brief gives partners and reviewers a compact entry point into VSC Core 2.x.
+
+It is designed to be short enough for email sharing or PDF export.
+
+It is not a certification.
+
+It does not start v3.0.
+
+## One-sentence summary
+
+```text
+VSC turns AI decision states into portable, verifiable evidence.
+```
+
+## Current status
+
+VSC Core 2.x is review-ready.
+
+It includes:
+
+- a Go verifier
+- Node / Go comparison flow
+- machine-readable JSON verification results
+- conformance fixture comparison
+- CI conformance workflow
+- CI artifact upload
+- human-readable proof-boundary documentation
+- partner / reviewer interop documentation
+- enterprise review package
+- critical code-path comments
+
+The correct status is:
+
+```text
+Review-ready, not certified.
+```
+
+## Core proof boundary
+
+```text
+VSC proves state integrity, not truth.
+```
+
+VSC can help verify whether a VSC evidence bundle is internally consistent and reconstructable.
+
+VSC does not prove that an AI decision was true, fair, legal, compliant, morally correct, or externally attributable.
+
+## Result interpretation
+
+```text
+PASS  = VSC state evidence is internally consistent.
+FAIL  = VSC integrity or verification mismatch detected.
+ERROR = Verification could not complete.
+```
+
+Important:
+
+```text
+PASS does not mean truth.
+FAIL does not mean wrongdoing.
+ERROR is distinct from FAIL.
+```
+
+## Reproducibility commands
+
+Reviewers can run:
+
+```powershell
+npm run vsc -- compare:fixtures
+```
+
+Expected:
+
+```text
+Final result: COMPARE_PASS
+```
+
+Reviewers can also run:
+
+```powershell
+npm run vsc -- compare:fixtures --json
+```
+
+Expected JSON field:
+
+```json
+{
+  "result": "COMPARE_PASS"
+}
+```
+
+Full verification:
+
+```powershell
+npm run vsc -- verify-all
+```
+
+Expected high-level summary:
+
+```text
+FAIL: 0
+```
+
+## What COMPARE_PASS means
+
+```text
+COMPARE_PASS means the comparison runner and verifier agree on expected fixture result classes.
+```
+
+It does not mean:
+
+- real-world truth
+- legal correctness
+- fairness
+- compliance
+- external artifact validity
+
+## Interop model
+
+VSC can reference external artifacts while keeping proof domains separate.
+
+Safe interpretation:
+
+```text
+TBN      = identity / trust verification
+VSC      = decision-state verification
+CLARIXO  = responsibility / attribution context
+```
+
+Core interop rule:
+
+```text
+VSC can point outward without taking over external proof domains.
+```
+
+Related boundary:
+
+```text
+External references are pointers, not proof imports.
+```
+
+## What an external reference means
+
+An external reference means:
+
+```text
+VSC points to an external artifact as context.
+```
+
+Examples:
+
+- TBN receipt reference
+- CLARIXO record reference
+- external audit note reference
+- partner evidence record reference
+
+## What an external reference does not mean
+
+An external reference does not mean:
+
+- VSC verified the external artifact
+- VSC imported the external proof claim
+- VSC proved identity
+- VSC proved attribution
+- VSC proved legal responsibility
+- VSC proved compliance
+- VSC proved truth
+- VSC completed production integration with the external system
+
+## Suggested partner review path
+
+Suggested first review path:
+
+1. Read this brief.
+2. Read the enterprise review package.
+3. Run the reproducibility commands.
+4. Inspect the technical verification path.
+5. Inspect the interop boundary documents.
+6. Confirm whether the proof boundaries are clear enough for your use case.
+7. Identify whether your system should reference VSC, be referenced by VSC, or require a separate verifier.
+
+## Key documents
+
+Main review package:
+
+```text
+docs/review/ENTERPRISE_REVIEW_PACKAGE.md
+```
+
+Partner / reviewer interop brief:
+
+```text
+docs/interop/PARTNER_REVIEWER_INTEROP_BRIEF.md
+```
+
+Interop consolidation summary:
+
+```text
+docs/interop/INTEROP_CONSOLIDATION_SUMMARY.md
+```
+
+PASS / FAIL explanation:
+
+```text
+docs/non-technical/PASS_FAIL_EXPLAINED.md
+```
+
+Executive one-pager:
+
+```text
+docs/non-technical/EXECUTIVE_ONE_PAGER.md
+```
+
+## Suggested partner questions
+
+Partners may answer:
+
+- What artifact does your system produce?
+- What proof claim does your system make?
+- Should VSC reference your artifact only?
+- Should your artifact require a separate verifier?
+- What identifier, hash, or URI should VSC record?
+- Which proof boundary must remain outside VSC?
+- What wording would avoid overclaiming?
+
+## Explicit non-claims
+
+VSC does not claim:
+
+- formal certification
+- production enterprise certification
+- legal compliance
+- legal responsibility proof
+- truth proof
+- identity proof
+- attribution proof
+- fairness proof
+- external artifact validation
+- completed TBN / VSC / CLARIXO integration
+- v3.0 start
+
+## Suggested next step
+
+A useful next step is an external review session using:
+
+```text
+docs/review/ENTERPRISE_REVIEW_PACKAGE.md
+```
+
+The review should focus on reproducibility, boundary clarity, CI behavior, result interpretation, and partner handoff assumptions.
+
+## Summary
+
+VSC Core 2.x is positioned as:
+
+```text
+Review-ready, not certified.
+```
+
+The central rule remains:
+
+```text
+VSC proves state integrity, not truth.
+```