Project: DigiEmu VSC / VSC Core
Release context: v2.24
Status: documentation-only consolidation
This document consolidates the VSC interop work completed from v2.17 through v2.23.
It is a summary document.
It does not add verifier behavior.
It does not implement external reference validation.
It does not create fixtures.
It does not start v3.0.
It does not change the VSC proof boundary.
VSC proves state integrity, not truth.
External references are pointers, not proof imports.
Reference validation is not artifact validation.
Shape validation checks the reference object, not the external artifact.
Fixture planning does not implement fixture validation.
v2.17 — TBN / VSC / CLARIXO boundary notes
v2.18 — External Reference Profile Draft + JSON Schema
v2.19 — External Reference Examples
v2.20 — External Reference Validation Notes
v2.21 — Interop Roadmap / Pre-v3 Planning
v2.22 — External Reference Shape Validation Plan
v2.23 — External Reference Fixture Plan
| Document | Release | Role | Status |
|---|---|---|---|
docs/interop/TBN_VSC_CLARIXO_BOUNDARIES.md |
v2.17 | Layer separation and safe boundary language | Documentation |
docs/interop/EXTERNAL_REFERENCE_PROFILE_DRAFT.md |
v2.18 | Draft external reference profile | Draft profile |
schemas/external-reference-profile-v2.18-draft.schema.json |
v2.18 | Draft JSON Schema for external references | Draft schema |
examples/external-references/ |
v2.19 | Typed external reference examples | Examples |
docs/interop/EXTERNAL_REFERENCE_VALIDATION_NOTES.md |
v2.20 | Shape-vs-proof validation boundary | Documentation |
docs/interop/INTEROP_ROADMAP_PRE_V3.md |
v2.21 | Staged roadmap and v3.0 gate | Planning |
docs/interop/EXTERNAL_REFERENCE_SHAPE_VALIDATION_PLAN.md |
v2.22 | Candidate shape-validation cases | Planning |
docs/interop/EXTERNAL_REFERENCE_FIXTURE_PLAN.md |
v2.23 | Candidate fixture classes | Planning |
The existing VSC implementation continues to support its current evidence and verification workflows.
The interop work from v2.17 to v2.23 does not add new verifier behavior.
Implemented technical foundation remains focused on VSC evidence-bundle integrity and existing verification flows.
The external reference profile is draft:
docs/interop/EXTERNAL_REFERENCE_PROFILE_DRAFT.md
schemas/external-reference-profile-v2.18-draft.schema.json
The draft profile defines how VSC-related metadata may point to external artifacts.
It does not make those external artifacts part of the VSC proof boundary.
The example files are located in:
examples/external-references/
These examples show safe reference-object shapes.
They are not production integrations.
They are not conformance fixtures.
They do not prove external artifact validity.
The following documents are planning-only:
docs/interop/INTEROP_ROADMAP_PRE_V3.md
docs/interop/EXTERNAL_REFERENCE_SHAPE_VALIDATION_PLAN.md
docs/interop/EXTERNAL_REFERENCE_FIXTURE_PLAN.md
They describe possible future directions.
They do not implement validation behavior.
They do not create fixtures.
They do not start v3.0.
VSC does not prove:
- truth
- identity
- legal guilt
- legal responsibility
- responsibility attribution
- fairness
- full compliance
- issuer authority
- external artifact validity
- external timestamp authority
- TBN receipt validity
- CLARIXO record validity
- audit conclusion correctness
- partner evidence trustworthiness
These remain outside VSC unless a separate external verifier and profile are explicitly defined.
Safe:
VSC can reference external artifacts while preserving its proof boundary.
Safe:
A reference object may identify external context, but VSC does not import the external proof claim.
Safe:
Future shape validation, if implemented, would check the reference object only.
Unsafe:
VSC verifies TBN receipts.
Unsafe:
VSC proves CLARIXO attribution.
Unsafe:
External reference validation proves external artifact truth.
Unsafe:
The v2.x interop arc means v3.0 has started.
A compact partner-facing entry point is available in:
docs/interop/PARTNER_REVIEWER_INTEROP_BRIEF.md
This brief summarizes the interop model without adding implementation scope.
After this consolidation, the project can choose among several safe next directions:
- pause and treat the v2.x interop arc as stable documentation
- prepare partner-facing summary material
- perform a v3.0 architecture review
- plan actual external reference fixtures in a future release
- plan reporting language for external references
Any next step should preserve the existing proof boundaries.
The v2.17 to v2.23 interop arc gives VSC a safe language and planning foundation for external references.
It does not expand VSC's proof claims.
The central rule remains:
VSC can point outward without taking over external proof domains.